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

Annotations already declare readOnlyHint, idempotentHint, destructiveHint=false and openWorldHint=false, so the safety profile is fully covered. The description adds meaningful context the annotations do not: what each result contains (part number, the source document that attests fit, and the series scope), which matters because there is no output schema. It does not disclose result counts, pagination, or behaviour when no fitting part exists.

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 sentence, front-loaded with the core resource, and every clause carries information. The nested parenthetical listing document types is slightly heavy for a single sentence but is not wasted text.

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 no output schema, the description usefully compensates by enumerating the returned fields, including the provenance document. Gaps remain around result volume, pagination, and the empty-result case, which keeps it from a 5.

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?

There is a single parameter with 100% schema description coverage, and the schema already documents the 'maker/model' format with an example. The description implies the robot argument drives fit and series scoping but adds no syntax or matching behaviour (e.g. fuzzy vs exact) beyond the schema. 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 description states a specific resource and its compatibility scope: spare parts that fit a given robot, with the parts scoped to a series. That is unambiguous and clearly distinct from siblings like find_robots, get_robot, or compare_robots, which operate on robots rather than parts. It lacks an explicit verb ('find'/'list') and never names a sibling, so it stops short of 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?

There is no when-to-use guidance, no statement of prerequisites, and no mention of alternatives among the six sibling tools. An agent must infer from the resource alone that this is the right call when it needs parts rather than robot metadata.

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