get_anim_curves

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

No annotations are provided, so the description carries the transparency burden. 'Get' implies a read-only operation, and the description adds the filter behavior. It doesn't disclose error handling or side effects, but the output schema covers return structure, which mitigates the gap.

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 concise and front-loaded: a one-sentence purpose followed by a clear Args section. Every sentence earns its place without redundant elaboration.

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 simplicity of the tool and presence of an output schema, the description is largely complete. It could explicitly note that it only returns curves and nothing else, but the purpose and parameters are adequately covered for a getter.

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 has no descriptions (0% coverage), but the description fully compensates by explaining both parameters: asset_path as 'Unreal asset path' and curve_type with allowed values 'float', 'vector', or 'transform'. This adds meaning beyond the bare schema.

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 'Get all curves on an animation sequence' with a specific verb and resource. It distinguishes from sibling tools by focusing on curves, though it doesn't explicitly contrast with other get_ tools.

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 implies usage when you need curves, and the curve_type filter adds context. However, it does not explicitly state when to use this tool versus alternatives or mention any exclusions, so guidance is only implied.

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