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

Goes well beyond the destructiveHint/openWorldHint annotations by explaining partial-update semantics, array-replacement-and-clear behavior, silent dropping of unknown stack_layer_ids, and rejection of invalid status transitions. The only small gap is that it never spells out the response shape or that clearing arrays is an irreversible data-loss operation the destructiveHint implies.

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?

Purpose is front-loaded and no sentence is filler; the ID-lookup sentence is dense but carries real routing value. A few run-on constructions (semicolon-chained rejection rules) could be broken up for faster scanning, but nothing is redundant.

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?

For a mutation tool with nested oneOf params and a destructive hint, the description covers creation requirements, update diffing, rejection rules, and ID discovery. The missing piece is what comes back after a successful call (e.g., new task_id), which matters since there is no output schema.

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 the baseline would be 3; the description earns extra credit by explaining semantics the schema cannot convey—omitted fields stay unchanged, supplied arrays replace stored lists, [] clears them, and unknown stack_layer_ids are dropped. It still does not explain what a successful create returns or how depends_on references are validated.

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 first sentence states a specific verb pair and resource ('Create or update tasks within an Epic') and the title/description together make clear that both create and update are handled through the action parameter. An agent can distinguish this from list_tasks or start_task without opening the schema.

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?

Explicitly names the calling context (Planner Breakdown step) and tells the agent exactly how to obtain prerequisite IDs via query_context domain=backlog with concrete action examples, which is the natural alternative tool to consult first. It also states rejection conditions (empty update, active/claimed task) that gate whether the agent should call the tool at all.

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