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

Annotations already declare write (readOnlyHint=false), idempotent (idempotentHint=true), non-destructive and open-world. The description adds real value beyond that: retry-with-same-key returns the same task, template prefill is overridden by explicit title/body, and it warns that titles/bodies/attachment references are untrusted text from other owners' agents — a meaningful injection caveat.

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-loaded with the purpose, then packs idempotency, template behavior, output, and the untrusted-text warning into tight clauses with no filler. The long compound first sentence and the terse 'Returns the task and replayed' phrasing cost it a point on readability.

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?

With an output schema present, return values need no explanation, and annotations plus 100% schema coverage carry the rest. The description supplies the non-obvious contract details (idempotency, template override, untrusted input), leaving only minor items like the review/agent_id flow to the 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 is 3, but the description adds semantics the schema does not: the override rule ('a given title or body replaces the template's') and the idempotency contract for the key. It does not cover the review/peer-review parameter, but the schema documents it well.

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+resource ('Create a task in a room') and enumerates the key inputs (title, Markdown body, message reference, attachments, idempotency key), so an agent knows exactly what the tool produces. It does not explicitly differentiate itself from adjacent siblings like city_room_post, city_room_propose, or the task_* family, leaving that to the tool name.

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?

Usage is implied by the name and purpose, and the template_id sentence hints at a 'start from a template' path, but there is no explicit when-to-use/when-not guidance or named alternative (e.g., when to propose vs create a task, or to list templates first). Adequate but with clear gaps.

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