set_task_blocker

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

Since no annotations are provided, the description must disclose behavior. It explains that the tool toggles the blocker relationship (adds or removes) and clarifies the direction relative to taskId. This is transparent enough for the tool's simple operation, though it could mention what happens on success or failure.

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 only two sentences, front-loaded with the main purpose, and every sentence adds value. There is no wasted wording.

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 simplicity (3 required parameters, no output schema), the description covers the core functionality, direction semantics, and ID formats. It lacks mention of what the tool returns or side effects, but for a toggle action, this is nearly 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?

The input schema has 0% description coverage, so the parameter semantics depend entirely on the description. It adds meaning by stating that taskId and blockerTaskId accept database IDs or HRIDs (e.g., 'PRJ-21'), and explains the two direction values ('blockers' = tasks blocking taskId, 'blocking' = tasks taskId blocks). This fully compensates for the lack of schema descriptions.

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 'Toggle a blocker relationship between two tasks,' which is a specific verb and resource. It distinguishes from sibling tools like create_task and edit_task by uniquely describing this relationship manipulation.

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 explains the direction parameter and ID formats, but does not explicitly state when to use this tool versus alternatives or provide any exclusions. The guidance is adequate for a straightforward action but lacks comparative context.

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