quire.deleteStatus

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

The description discloses the destructive action (confirmed by destructiveHint=true) and explains that tasks with the deleted status will be reverted to To-Do. It also adds the restriction on deleting default statuses, which goes beyond the annotation.

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?

Two sentences, no unnecessary words. The description is front-loaded with the primary action and includes key behavioral information 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 simple delete tool with two required parameters and no output schema, the description covers the core action, side effects (task reversion), and constraints (default statuses protected). It is fully adequate for agent understanding.

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 already describes both parameters with their constraints (e.g., value must be 1-99). The description reiterates the deletion constraint but adds no new parameter-specific detail beyond what the schema provides. Schema coverage is 100%, so baseline is appropriate.

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 specifically states 'Delete a custom status' and explains the effect on tasks. It clearly distinguishes from siblings like createStatus and updateStatus by indicating what happens to tasks with the deleted status.

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 guidance on when to use (for custom statuses) and explicitly states that default statuses (0 and 100) cannot be deleted. However, it does not mention alternative tools for other status management actions.

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