add_distance_mate

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

No annotations are provided, so the description carries the full burden. It does not disclose behavioral traits such as whether the mate is destructive, if it can be removed, permission requirements, or behavior when over-constrained. It mentions 'Returns the created mate's metadata' but lacks detail on what that includes.

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 relatively concise but contains redundant Spanish and English text. The key information is front-loaded in the English portion. It is structured with an Args section and a Related line, making it scannable.

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?

Given the tool has 6 parameters, no output schema, and moderate complexity, the description is incomplete. It does not explain the entity IDs, component names, or align parameter. The reference to add_concentric_mate assumes knowledge of that tool. No return value details beyond 'metadata'.

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 0%; the description explicitly only defines distance_mm (with unit) and refers to other arguments as 'same as add_concentric_mate,' providing minimal additional meaning. The align parameter with default is not explained, and entity/component parameters are not elaborated.

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 clearly states the tool adds a distance mate (fixed offset) between two entities, and provides specific use cases (parallel plate separation, bearing-to-bearing distance). It distinguishes from sibling mates like add_concentric_mate and add_angle_mate by focusing on fixed offsets.

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?

The description gives typical use cases and explicitly lists related tools (add_mate_by_face_position, stack_components) that offer alternatives or convenience. However, it does not explicitly state when not to use this tool.

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