set_time_config

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

With annotations indicating destructiveHint=true and readOnlyHint=false, the description adds concrete behavioral context by warning that keyframes get resampled if the tool is not set before animating. This goes beyond the annotation flags and gives the agent a specific side effect, while not contradicting the annotations.

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, with the core function in the first sentence and the critical usage warning in the second. The bilingual repetition is acceptable and adds no extra noise. Every essential piece of information is present without fluff.

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 simplicitycars, the schema fully documents all parameterscars, and annotations indicate the destructive nature, the description provides sufficient context including the keyframe resampling warning. It does not need to describe return values since there is no output schema. The only minor gap is not clarifying the implied interdependence of startFrame and endFrame, but the description covers the core requirement.

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?

All four parameters have descriptive entries in the schema, so the baseline is met. The description does not add extra parameter semantics beyond mapping the frame rate and time range to the corresponding fields. It does not clarify relationships between parameters or mention playbackSpeed explicitly.

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 function: setting frame rate and animation time range. It uses a specific verb and resource, which unambiguously conveys what the tool does. It does not explicitly name the sibling tool get_time_config, but the 'set' versus 'get' contrast is implied.

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 explicit usage guidance: 'Set this before animating, otherwise keyframes get resampled.' This clearly states when the tool should be used and warns of the consequence of not using it. It does not discuss alternatives like get_time_config, but the context is clear.

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