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

With no annotations, the description carries the full burden and does so: it discloses the side effect (emails every expert in the task's pools), the count/scope (once), irreversibility ('cannot be undone'), the confirmation gate, and the failure behavior (returns a list of anything missing). This is exactly the behavioral context an agent needs before a destructive-ish broadcast.

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 tight sentences, front-loaded with what the tool does and immediately followed by the irreversibility warning and the required precondition. No filler; every clause adds decision-relevant information.

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 tool with no annotations and no output schema, the description covers action, side effects, irreversibility, precondition, and error shape. It could say more about the resulting task state (e.g. what status it moves to, whether it can be re-published), but nothing critical is missing.

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 0%, so the description must compensate. It explains confirm well, including why it exists (explicit user confirmation) beyond the schema's const: true. taskId is left unexplained, though its name and uuid format make its meaning self-evident.

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 specific verb and resource ('Open a task for experts'), making the state-changing action clear. It does not explicitly contrast with close_task or create_task among siblings, so an agent must infer the lifecycle position, but the action itself is unambiguous.

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: call only after the user explicitly confirmed, with confirm: true. That is strong usage guidance. It stops short of naming alternatives (e.g. create_task for drafts) or stating when not to call, so it is clear context without full routing.

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