add_rest

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

With no annotations provided, the description carries the full burden of behavioral disclosure. It only notes that the tool adds a rest and takes a duration, but does not mention side effects (e.g., overwriting existing notes), permission requirements, or the exact meaning of 'current position'. The return value is vaguely described as 'Success status'.

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 extremely concise with two sentences and a parameter docstring, all focused on essential information. No extraneous content, and the main purpose is 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 (one optional parameter) and the existence of an output schema, the description covers the basic functionality and parameter meaning. However, it lacks context on the operational environment (e.g., 'current position' meaning) and prerequisites, which slightly reduces completeness.

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 description adds meaning to the 'duration' parameter by listing possible values (whole, half, quarter, etc.), which compensates for the 0% schema description coverage. However, it does not clarify if these are exact strings or case-sensitive.

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 adds a rest at the current position, specifying the action and resource. It distinguishes itself from sibling 'add_' tools like add_notes or add_articulation by focusing on rest, though it doesn't explicitly contrast with them.

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 no guidance on when to use this tool versus alternatives, nor does it mention prerequisites or restrictions. For example, it doesn't indicate if a score must be open or if the cursor must be at a valid position.

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