get_value_at_time

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

Annotations already provide readOnlyHint=true, idempotentHint=true, and destructiveHint=false, which convey safe, read-only behavior. The description adds the key behavioral detail 'interpolated' (not raw keyframe value), which is essential but not covered by annotations. No contradictions.

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, focused sentence that efficiently conveys the tool's purpose and behavior. Every word adds value, and there is no extraneous information. It is appropriately front-loaded.

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, strong annotations, and high schema coverage, the description is largely complete. It explains the core functionality but could benefit from mentioning what happens when no keyframes exist or when the time is out of range. Still, it provides sufficient context for most use cases.

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 coverage is 100%, and all four parameters have clear descriptions in the schema. The description adds no additional meaning beyond what the schema already provides (e.g., node_id, effect_name, time_seconds, property_name). Baseline score of 3 is 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?

The description 'Get the interpolated value of an effect property at a specific time' uses a specific verb ('get') and clearly identifies the resource ('interpolated value of an effect property') and context ('at a specific time'). It distinguishes this from sibling tools like 'get_effect_properties' or 'get_keyframes' by focusing on a single interpolated value at a given time.

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 for querying a single interpolated value, but it does not explicitly state when to use this tool versus alternatives like 'get_effect_properties' or 'get_keyframes'. There is no guidance on when not to use it or which sibling tools are better suited for different scenarios.

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