rigging_delete

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

The description does not disclose any behavioral traits beyond 'delete'. There is no mention of irreversibility, required permissions, side effects, or acknowledgment of the destructive nature. Since no annotations are provided, the description carries full burden and fails to add necessary context.

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 sentence, which is concise but not particularly helpful. It meets minimal requirements but does not earn its place with additional valuable information.

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 destructive nature and lack of annotations or output schema, the description should provide more context about deletion effects, prerequisites, or error conditions. It is incomplete for safe and informed agent usage.

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 100% coverage for its single 'id' parameter, including a description. The tool description adds no additional meaning beyond what the schema already provides. Per guidelines, baseline is 3 for high coverage.

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 explicitly states it deletes a rigging task. The verb 'delete' and resource 'rigging task' clearly distinguish it from sibling tools like 'rigging_create' or 'rigging_get'. However, it does not elaborate on what constitutes a rigging task in this context.

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?

No guidance is provided on when to use this tool versus alternatives, such as when a task should be deleted or any prerequisites. The description lacks context about typical usage scenarios.

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