add_distance_mate

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

With no annotations, the description carries full burden. It states 'fixed offset' and 'returns metadata' but does not disclose side effects, permissions, reversibility, or other behavioral traits beyond the basic function.

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 but includes redundant Spanish and English versions. It could be more concise without losing essential 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?

For a tool with 6 parameters and no output schema, the description is incomplete. It explains distance_mm but omits meanings for align, entity IDs, and component names, and only vaguely mentions return value.

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?

Only distance_mm is described ('fixed distance in millimeters'). The description references 'other args: same as add_concentric_mate' without elaboration, leaving 5 out of 6 parameters undocumented. With 0% schema coverage, the description insufficiently compensates.

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 it adds a distance mate (fixed offset) between two entities, and gives specific use cases (parallel plate separation, bearing distance, controlled gap). It distinguishes from siblings by mentioning related tools like add_concentric_mate, add_mate_by_face_position, and stack_components.

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?

Provides typical use case context and references sibling tools for comparison (e.g., 'same as add_concentric_mate', 'related: add_mate_by_face_position'). However, it does not explicitly state when not to use this tool or provide clear exclusions.

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