update_task_header

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

The description adds the partial update hint, which is not in annotations. Annotations already declare idempotentHint=true and destructiveHint=false, so the description complements this without contradiction. No further behavioral details (e.g., auth, rate limits) are provided.

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 sentence that immediately conveys the tool's purpose. Every word is necessary, and there is no filler content.

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?

While the purpose is clear, the description lacks information about return values (no output schema), prerequisites (e.g., header must exist), and potential side effects beyond annotations. Given the tool's simplicity, it is minimally adequate but not comprehensive.

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%, so all parameters are documented. The description reinforces partial update semantics ('only send fields you want to change'), but adds no new details about individual parameters beyond the 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 'Update a task header,' specifying the action and resource. This distinguishes it from sibling tools like update_task (which updates a task) and create_task_header/delete_task_header.

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 includes 'Only send the fields you want to change,' which implies partial update usage. However, it does not provide explicit guidance on when to use this tool versus alternatives like update_task or when not to use it.

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