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

Annotations already declare readOnlyHint=true and openWorldHint=false, so safety is covered. The description adds one genuinely useful behavioral trait — matching is fuzzy, not exact — and the mandatory pre-call positioning, but says nothing about multiple matches, ranking of near-matches, or what the agent should do with an ambiguous result.

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 filler, with the core purpose first and the ordering rule second. Nothing could be removed without losing information.

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?

Adequate for a one-parameter read-only lookup whose annotations carry the safety profile and which has no output schema to explain. The remaining gap is disambiguation behaviour — what a partial or multi-match returns and whether the resulting contact id is what downstream draft tools need — which would materially help an agent chain the call.

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?

Schema coverage is 100% and there is only one parameter, so baseline is 3; the description earns a bump because "fuzzy-search" tells the agent to pass a plain name rather than an exact string or wildcard pattern, which affects how the value should be formed.

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?

States a specific verb and matching mode ("fuzzy-search") plus the resource ("existing client/contact") and the key field (name). An agent can immediately distinguish it from create_contact or query_clients.

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?

Gives an explicit ordering rule and names the three sibling tools it must precede (create_invoice_draft, create_quote_draft, log_time) with the trigger condition "when a client is mentioned." It does not say what to do when no match is found (create_contact?) or when query_clients would be preferable, so the when-not half is absent.

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