Find Client Profile

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

The description is consistent with the readOnlyHint=true annotation, confirming it is a read-only operation. It discloses the matching logic (exact then substring) and the null return case. No contradictions with annotations.

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?

The description is extremely concise with two sentences that front-load the core action 'Look up'. Every word serves a purpose, with no redundancy or filler.

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?

The description adequately explains the tool's purpose and behavior for a lookup without an output schema. It mentions the return type (profile or null), which is sufficient. However, it could optionally hint at the profile structure, but that is not critical.

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?

Although the schema already describes the query parameter as 'client_id, or part of the display name', the description adds value by explicitly stating the exact match priority and case-insensitive substring fallback. This goes beyond the schema's minimal description.

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?

The description clearly states the tool's function: looking up a client profile by exact client_id or case-insensitive display_name substring. It specifies the return behavior (profile or null) and distinguishes it from sibling tools like save_client_profile (write) and list_client_reports (list).

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?

The description provides clear context on when to use this tool (lookup by client_id or display_name substring) but does not explicitly mention when not to use it or offer comparisons to alternative tools like search. However, the matching logic is well-explained.

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