add_concentric_mate

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

No annotations provided, so description carries full burden. Discloses locale sensitivity for entity names, align parameter, and return of mate metadata. However, lacks details on error handling or side effects (e.g., does it modify assembly state?). Still adds significant behavioral context.

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?

Well-structured with bullet points and bilingual content. Could be slightly more concise by omitting Spanish repetition, but front-loads core purpose and uses clear formatting.

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 all 5 parameters, required fields, typical usage, return value, and related tools. No output schema, but description adequately describes return as mate metadata. Complete for a mate tool with moderate complexity.

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 0%, so description compensates fully. Explains each parameter: component names from get_active_assembly_info, entity ID strings (locale-sensitive), and align values. Provides context beyond schema (e.g., copy verbatim note).

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?

Clearly states it aligns axes of cylindrical/conical entities via a concentric mate. Provides specific verb ('alinea ejes' / 'align axes') and resource. Distinguishes from siblings like 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?

Explicitly describes typical autoparts use cases (bolt+sleeve, sleeve+shaft, two bearings). Mentions related tools for alternative approaches, giving clear when-to-use guidance.

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