rlm_htask_block

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

No annotations provided. Description mentions automatic propagation to ancestors if is_blocking=true, but does not disclose side effects on task state, permissions needed, or other behavioral traits.

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 with no waste. Clearly states purpose, requirements, and key behavior.

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?

With 8 params (4 required) and no output schema, description should cover more semantics and side effects. It mentions propagation but omits details on enum values, optional fields, error conditions, or response.

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 100% (baseline 3). Description adds minimal value by naming required params and propagation condition but does not elaborate beyond schema.

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?

Description uses specific verb 'Block' with resource 'task' and mentions 'detailed payload'. It distinguishes from sibling 'rlm_htask_unblock' by being the blocking action.

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?

Description implies usage context (blocking a task with reason) but lacks explicit when/not to use or comparison with alternatives like unblock. It mentions requirements but no exclusions.

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