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

Beyond the annotations, the description explains the geometric distance semantics, rotation/scale invariance, practical distance thresholds, and the PRO subscription requirement. This gives the agent substantial behavioral context for interpreting results and knowing when the tool is appropriate.

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 description is front-loaded with purpose and metric semantics, then adds practical guidance and prerequisites. Every sentence carries useful information, with no redundant restatement of the schema or annotations.

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 similarity lookup with fully described parameters and annotations, the description supplies the remaining needed context: distance interpretation, invariance, threshold guidance, UUID source, and subscription requirement. Nothing essential for correct invocation is missing.

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 100%, so the parameters are already well documented. The description adds useful semantics by reinforcing that partRevisionId is a UUID and pointing to query(entity="partRevision"), plus a practical near-duplicate threshold for maxDistance.

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 opens with a specific verb and resource: 'Find the part revisions most similar in shape to a given one.' It distinguishes this from sibling tools by directing agents to inspectPartRevision for real dimensions and query for finding the UUID, so the intended scope is immediately clear.

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?

It clearly explains the shape-similarity use case, provides the alternative inspectPartRevision for real dimensions, and tells agents how to obtain the required UUID via query. It does not explicitly state every when-not condition, but the usage context and prerequisite are well covered.

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