anim.report

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

The description explicitly states the tool is 'read-only', which is a key behavioral trait. However, with no annotations, it fails to disclose error behavior, required permissions, or what happens when the object is invalid. The safety implication is partially covered but lacks depth.

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 a single, front-loaded sentence that conveys all essential purpose and behavior without any wasted words. Every part earns its place.

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's simplicity (one optional parameter, no output schema), the description covers the key information: what is reported and that it's read-only. It is slightly incomplete by not specifying output format or error handling, but sufficient for basic understanding.

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%, meaning the parameter 'object' has no description in the schema. The tool's description does not mention the parameter at all, so it adds no meaning beyond the schema's title. The agent must rely on the parameter name alone.

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 produces an animation report for an object, specifically listing frame range and f-curve count. It distinguishes itself from sibling animation tools by specifying read-only reporting, unlike tools that modify or list actions/keyframes.

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 provides no guidance on when to use this tool versus alternatives like anim.list_actions or anim.keyframes. It does not mention exclusions or prerequisites, leaving the agent to infer usage from context.

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