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

Annotations already flag destructiveHint/readOnlyHint/openWorldHint, and the description layers on genuinely new behavior: the thread moves to refine_pending, refinement re-plans roadmap items, can edit or HARD-DELETE previously generated task rows, and there is a cap of five refinements per thread. This is exactly the kind of consequence detail an agent needs before calling a destructive tool.

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?

Front-loads the intent then packs the constraints into a few tight sentences with no filler. The parenthetical about the machine patch-tasks endpoint is slightly tangential but still earns its place as a destructiveness explanation.

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?

Output schema exists so return values needn't be described, and the description covers the state transition, the destructive side effects and the call cap. The main gap is the meaning/scope of thread_id and project_id, which matters for a 3-required-parameter tool.

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 0%, so the description carries the parameter burden. It does usefully constrain feedback_md (1..1979 chars), but says nothing about project_id or thread_id, leaving two of three required parameters undocumented in both schema and description.

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?

States a concrete verb+resource ('say what is wrong... have it reworked') and names the artifact affected (request output, roadmap items). It is distinguishable from adjacent tools like answer_request, get_request_status and replan_task, though it never explicitly contrasts itself with them.

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?

Gives a hard precondition ('Status must be "done"') and routes the agent to get_request_status to observe the revised items. It stops short of naming alternatives or when-not-to-use cases (e.g. vs. answer_request or replan_task), which keeps it out of 5 territory.

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