clearance

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

Discloses that a result of 0 indicates touching/overlapping and suggests an alternative, but does not explicitly state the tool is read-only or mention side effects. However, the description adds value beyond missing annotations.

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?

Three concise sentences: purpose, behavior/alternatives, parameter definition. No unnecessary text, front-loaded with key 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?

Covers input, output meaning, and alternative tool. Lacks error scenarios or edge cases (e.g., missing shape names), but given low complexity and presence of output schema, it is reasonably complete.

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?

With 0% schema description coverage, the description adds essential context that parameters are names from show(), partially compensating for the lack of schema documentation. Further detail about format or validation could improve clarity.

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?

Description clearly states the tool returns the minimum distance between two named shapes, specifying units (mm) and distinguishing from the sibling 'interference' tool for overlap detection.

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?

Explicitly tells when to use (to get minimum distance) and when to use alternative (interference for overlap), with a clear condition (result of 0 indicates touching/overlapping).

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