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

Annotations already declare readOnly=true, idempotent=true, destructive=false and closed-world, so the safety profile is covered. The description adds genuinely useful behavioral semantics — partial and case-insensitive matching — but says nothing about result caps, ordering, or behavior on zero matches.

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?

One front-loaded sentence with the matching semantics and a concrete example; no filler, nothing to trim.

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?

For a one-parameter lookup with full annotation coverage and no output schema, the description supplies the one non-obvious detail (fuzzy name matching). Result-shape expectations are the only unaddressed item, and the absence of an output schema keeps that a minor gap.

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 0% and the single parameter is an undocumented plain string, so the description carries the burden — and it does, specifying that the match is partial and case-insensitive, which an agent needs to know before invoking. It stops short of noting whether an empty string is valid or how multiple matches behave.

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 (Find) plus resource (vendors) and even the matching mode (partial, case-insensitive), which is more than a bare restatement. It does not distinguish itself from the sibling get_vendor, which is the only missing piece for a 5.

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 example ("a bank counterparty string") implies the intended use case of resolving an unstructured name to a vendor, but there is no explicit guidance on when to use this versus get_vendor or the other search_* siblings. Usage must be inferred.

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