remove_track

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

The description reveals destructive behavior (deletes auto-tasks), idempotency on retry, and the response format. This adds significant context beyond the annotations which only indicate destructiveHint=true.

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, with no redundant sentences. It front-loads the main action and provides essential details efficiently.

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 destructive mutation tool with no output schema, the description covers the action, side effects (auto-task deletion), idempotency, and response structure. It is complete.

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 50%, with the confirm parameter described in schema. The description reinforces confirm=true and adds idempotency details, but does not explain the id parameter. It adds some value but does not fully compensate for missing id description.

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 action: 'Remove a track instance from its entity.' It uses a specific verb and resource, and is distinct from sibling tools like 'update_track' or 'apply_track'.

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?

It explicitly requires confirm=true, warns about auto-task deletion, and advises copying needed details. It does not compare directly to alternatives but provides clear usage context.

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