rlm_htask_update

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

The description discloses whitelist enforcement and admin requirement, important behavioral traits. However, it does not mention error handling, idempotency, or return value behavior, which are gaps given no annotations.

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, front-loaded with main action, no filler. Every word adds value.

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?

The description covers key constraints but lacks output format, update behavior (merge or replace), and guidance on how to determine allowable fields per status. Given no output schema, more detail on return value is needed.

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 parameters are well-documented. The description adds context that fields are status-dependent, but does not provide specific field names or detailed update behavior 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?

The description clearly states the tool updates task fields, with specific constraints like whitelist based on status and admin requirement for structural fields. This distinguishes it from sibling tools like rlm_task_update and rlm_htask_create.

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 context on when to use: for updating fields under status-based whitelist and admin requirement. It lacks explicit comparison to siblings but implies hierarchical task context.

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