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

No annotations provided, so description bears full burden. It only states the basic action without disclosing side effects, reversibility, or whether it modifies state. Example shows parameter usage but not 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?

Two concise sentences, aliases, and an example. All information is front-loaded and relevant. No wasted words.

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 no annotations, incomplete schema descriptions, and an output schema whose content is not mentioned, the description is insufficient. Lacks parameter details, return value, and behavioral scope.

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 has 0% description coverage, so description must compensate. It provides axis options (x, y, z) and an example mapping parameters, but does not explain what 'frames' and 'degrees' mean semantically or their units.

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 'Spin/rotate the model around an axis (x, y, or z)', which is a specific verb and resource. The aliases and example reinforce clarity. Distinguishes from sibling 'record_spin' by mentioning combination with recording.

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?

Mentions use case for turntable animations with recording, but does not explicitly state when to use versus siblings or when not to use. Lacks alternative guidance, but purpose is reasonably clear.

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