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

Annotations already cover the safety profile (readOnly, idempotent, non-destructive, closed-world), so the bar is lower. The description adds only a light provenance hint ('verified' parts 'recorded' for a model), and says nothing about result counts, truncation, or what an empty result means.

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 no wasted words. It is efficient, though the brevity is part of why parameter and usage gaps remain.

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 3-param lookup with no output schema and 0% schema coverage, the description should say more: what 'brand' filters, what 'limit' bounds, and roughly what is returned. It covers the required 'model' param and the general return shape, but leaves the optional params and result semantics unaddressed.

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 0%, so the description must compensate for three undocumented params (model, brand, limit). It only conveys that 'model' must be exact; 'brand' and 'limit' are never explained in either place, leaving meaningful ambiguity for a filtering/pagination param.

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+resource ('Return verified appliance parts') and adds a meaningful constraint ('exact appliance model number'). However, it does not differentiate itself from siblings like lookup_part or lookup_substitution, so an agent must infer which of these to pick.

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 word 'exact' implies a usage condition (only pass a precise model number), which is useful implied guidance. But there is no explicit when-to-use/when-not-to-use statement and no sibling routing against lookup_part, lookup_substitution, or verify_fitment.

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