get_curve_keys

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

Annotations already declare readOnly/idempotent/destructive=false, so the safety profile is covered. The description adds meaningful behavior beyond that: it returns AUTHORED keys rather than interpolated values, and notes per-channel grouping plus counts, which clarifies the data shape.

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?

Front-loads the core action and pairs it with the alternative before the return listing. Slightly long, and the explicit 'Returns' enumeration is verbose, but with no output schema it 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?

For a single-parameter read tool with no output schema, the description supplies the return shape (field names), the semantic of the data (authored vs interpolated keys), and the sibling routing. Nothing needed to call it correctly is missing.

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% for the single curve_path parameter, so the schema carries the parameter documentation. The description adds no format or path-syntax detail beyond what the schema provides, making the baseline 3 appropriate.

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?

States a specific verb ('Read every keyframe') and resource ('curve asset') with the exact fields returned (time, value, interpolation mode) and grouping. It clearly distinguishes itself from add_curve_key (the write counterpart) and evaluate_curve_at_time (sampling).

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?

Explicitly routes the agent: 'to sample the interpolated value at an arbitrary time use evaluate_curve_at_time instead', and frames itself as the read-back oracle for add_curve_key before tuning. Names both the alternative and the condition that selects against it.

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