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

Annotations already declare readOnlyHint=true, destructiveHint=false and openWorldHint=true, so safety is covered. The description adds useful endpoint detail and the exactly-one selector rule, but says nothing about failure behavior (unknown id, no exact-name match, ambiguous names) or what a returned party contains.

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 terse sentences, zero filler, with the resource and lookup modes front-loaded and the constraint immediately after. Every clause carries 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?

For a two-parameter read with no output schema, this covers enough to invoke correctly: which selectors exist and that only one is allowed. The remaining gap is what happens on no match or non-exact name input, which matters for an exact-match lookup.

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 description coverage is 100% and both parameters are documented, so the baseline is 3. The description's "exact name" wording reinforces the schema's "Exact party name" but adds no new syntax or matching rules; the mutual-exclusivity rule it does add is modestly useful since the schema marks neither parameter required.

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 resource (one party) with its subtypes (customer, grower, supplier, owner) and the two lookup modes (by id or exact name), plus the underlying endpoints. It never names the sibling vintrace_list_parties, so the singular-vs-list distinction is inferable rather than explicit.

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?

"Give exactly one" sets a usage constraint, implying the agent should have an id or an exact name in hand before calling. No explicit when-to-use/when-not guidance and no pointer to vintrace_list_parties for fuzzy or partial name matching.

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