backlog_block_task

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

No annotations are provided, so the description bears full burden. It only states the basic purpose, omitting behavioral traits: whether the action is irreversible, what side effects occur (e.g., task disables), permissions needed, or idempotency. This renders transparency insufficient for an agent to predict outcomes.

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 barely informative sentence. While concise with no wasted words, it lacks structure and fails to front-load key details. It is not overly verbose, but the brevity comes at the cost of clarity.

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 complexity (3 parameters, 2 required), no output schema, no annotations, and many siblings, the description is critically incomplete. It does not explain the semantics of blocking, return values, or how this tool relates to similar ones. A tool with this profile requires more context for safe 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?

Schema description coverage is low (33%, only 'as' documented). The description adds no meaningful parameter-level guidance beyond the schema; it mentions 'blocking with a reason' but does not explain how 'id' or 'blocked_reason' should be used. With low schema coverage, the description should compensate but fails to do so.

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 verb 'blocking' and the resource 'task', indicating the tool marks a task as blocked with a reason. However, it does not distinguish this from sibling tools like backlog_complete_task or backlog_delete, which could be confused.

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 a conditional usage guide ('Use when blocking a task with a reason'), which implies when to use it but does not explicitly state when not to use it or mention alternative tools. Given the many siblings, this is minimal guidance.

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