Find Client Profile

Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?

Correctly declares readOnlyHint from annotations and adds matching behavior (exact client_id, case-insensitive substring for display_name). No contradictions.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Is the description appropriately sized, front-loaded, and free of redundancy?

Two sentences, zero waste, front-loaded with action and search behavior.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

Complete for a simple lookup: explains return value (profile or null), search behavior, and optional db_path. No output schema needed.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Adds meaning beyond schema: explains that query is interpreted either as exact client_id or case-insensitive substring for display_name. Schema coverage 100% so baseline 3, but extra detail elevates to 4.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Does the description clearly state what the tool does and how it differs from similar tools?

Description clearly states it looks up a client profile by exact client_id or case-insensitive display_name substring, distinguishing it from sibling tools like save_client_profile (write) or list_client_reports (lists reports).

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Does the description explain when to use this tool, when not to, or what alternatives exist?

Tells when to use (look up by id or name) and what it returns (profile or null). Doesn't explicitly exlcude cases, but implied for a simple lookup. No alternative mentioned but context clear.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.