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

Annotations already cover safety (readOnly, idempotent, openWorld=false, non-destructive), so the bar is lower. The description adds genuinely new behavioral context: the catalog is verified against cited manufacturer sources, and anything outside it is returned as 'unverified' AI-read data. That provenance/verification distinction is not present in any structured field.

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 purpose and the category instruction are front-loaded, which is good. But the massive mid-sentence enumeration of every category and sub-part is bloated, especially since an output schema exists and would return that catalog anyway; it reads like a data dump rather than an invocation aid.

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 read-only enumeration tool with an output schema, return-format detail is unnecessary and correctly omitted. The description covers scope, the optional filter, and the verified-vs-unverified behavior, which is enough to invoke it correctly; only the routing against siblings is absent.

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 the single optional 'category' param is fully documented in the schema, including the example value and the 'id from a previous list_coverage call' guidance. The description's 'Pass a category to list its models' restates rather than extends that, so baseline 3 applies.

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 opening sentence gives a specific verb and resource: listing product categories and models in the compatibility graph, with counts. The purpose is unmistakable, but it never names or contrasts a sibling tool (e.g. check_compatibility, find_parts), so it misses the sibling-differentiation bar 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?

'Pass a category to list its models' supplies a conditional usage pattern, which is more than nothing. However, it gives no when-to-use vs. the many check_* / find_parts siblings and no exclusions, leaving the agent to infer that this is the discovery entry point.

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