timer_add

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

No annotations are provided, so the description must fully disclose behavioral traits. It only states it adds a timer node and returns a success/error message. Missing details: potential side effects (e.g., overwriting existing nodes), required scene state, permissions, or whether it modifies the scene file directly. This is insufficient for a mutation tool.

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 well-structured with a clear purpose line, category, args list, and returns. It is concise for its content, though slightly verbose. The front-loaded purpose ensures quick understanding. It earns its place without redundancy.

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?

While the parameter descriptions are complete, the tool lacks context on preconditions (e.g., does the scene need to be open?), side effects (e.g., auto-save), and return details. With an output schema, the return description is minimal. For a simple addition tool, this is adequate but not thorough.

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 input schema has 0% description coverage, but the description lists each parameter with a brief explanation (e.g., 'wait_time: Time in seconds to wait before timeout signal'). This adds significant meaning beyond the schema's titles and defaults, fully compensating for the lack of schema descriptions.

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: 'Add a Timer node to a scene.' This is a specific verb+resource combination, and it distinguishes itself from siblings like 'node_add' (generic) and 'timer_configure' (modify existing).

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 when to use the tool (to add a timer node) but does not explicitly mention alternatives or when not to use it. For example, it doesn't suggest using 'timer_configure' for modifying existing timers. The guidance is adequate but lacks explicit context.

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