anim-keyframes

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

Since there are no annotations, the description must convey side effects explicitly. The word 'report' implies read-only, but it doesn't explicitly state that no modifications are made. It also doesn't describe error conditions or data limits.

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, clear sentence with no unnecessary words, making it highly concise and easy to understand.

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 explanation of the report format or content details. Without an output schema, the user is left uncertain about what the report will return, and there's no information about potential edge cases or limitations.

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?

The schema includes a single parameter 'object' with a title indicating it defaults to the active object, but no detailed description of the expected value or format. The description adds no additional semantic information about the parameter.

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's purpose as providing a detailed report on f-curves and keyframes for an object. It uses a specific verb ('report') and resource (f-curves/keyframes). However, it doesn't distinguish from other similar report tools like anim-report.

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 other animation-related tools. It doesn't mention any prerequisites, use cases, or criteria for selection.

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