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

No annotations are provided, so the description carries the full behavioral burden. It hints that deleting an in-use status has a dependency requiring a replacement, but does not disclose whether deletion is permanent/irreversible, what happens if no replacement is supplied while tasks use the status, or any permission requirements. For a destructive tool with zero annotation coverage this is a significant gap.

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 short sentences with zero waste, and the target-identification methods are front-loaded before the replacement condition. It is efficient, though extremely terse.

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 annotations and no output schema, the description should disclose permanence, error behavior when replacement is omitted, and permission needs. It covers only target identification and the replacement hint, leaving meaningful behavioral gaps.

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 100%, so the baseline is 3, but the description adds real value by clarifying the mutually exclusive lookup logic (statusId OR boardId+code) and the conditional use of replacementStatusId. That relationship is not spelled out in the schema itself.

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?

States a specific verb (delete) plus the resource (status) and two ways to identify the target (statusId or boardId+code). This distinguishes it from siblings like update_status or create_status without opening a schema. It stops just short of explicitly naming a sibling it is not.

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 conditional "If tasks use it, provide replacementStatusId" gives one genuine when-condition. However, there is no explicit guidance on when to choose this over update_status or transition_task_status, nor any stated prerequisite such as permissions.

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