quaternion_from_euler

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

Without annotations, the description carries full burden. It discloses the conversion to a normalized quaternion and the order parameter's role. However, it doesn't specify input validation, edge cases, or the output's exact structure, which is acceptable for a pure math conversion.

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?

One sentence with 14 words, no wasted text, and front-loaded with the main action. Every word is necessary.

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?

The description lacks details about the output format (e.g., array or object structure) and does not provide examples or edge cases. Given the tool's moderate complexity and no output schema, this is a gap.

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 100%, so baseline is 3. The description adds clarification that the order parameter specifies rotation order (first-to-last), which slightly enhances the schema's enum values but is not a major addition.

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 it converts Euler rotations in radians to a normalized quaternion, using a specific verb ('Converts') and resource. This distinguishes it from sibling tools like 'compose_transform_4x4' or 'radiansToDegrees'.

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?

No explicit when-to-use or alternatives are given beyond the generic purpose. The description implies usage for converting Euler angles to quaternions, but does not mention exclusions or scenarios where other tools might be preferred.

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