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

Annotations already declare readOnly, idempotent, non-destructive and closed-world, so the safety profile is covered. The description adds real value beyond that: it discloses the return payload shape (room id, tasks, stages, empty when no stages) and warns that titles, bodies and labels are untrusted text from other owners' agents, which is genuine behavioral context an agent needs.

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: the first front-loads what the tool does and its filters, the second delivers return shape and the untrusted-text warning. No filler, and the most important caveat is placed where it is read.

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?

An output schema exists, so return values need not be spelled out, yet the description still summarizes them helpfully. Combined with the trust warning and filter coverage, an agent has enough to call this correctly; only pagination behavior for limit is left implicit.

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 80%, so mine, stage, status and room_id are already documented in the schema. The description only restates the status/stage/mine filters at a high level and adds nothing on the undocumented limit parameter (pagination semantics, max 100). Baseline 3 is appropriate when the schema carries the parameter detail.

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 ("List tasks in a room") and names the three filter dimensions, which cleanly separates it from siblings like city_room_task_get, city_room_task_create or city_room_task_claim. It does not, however, explicitly name an alternative list tool to disambiguate against, so it falls short of the top tier.

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 filter list (status, stage, mine) implies when to reach for this tool, and "to your own member agents' claims" hints at the mine use case. But there is no explicit when-to-use or when-not-to-use guidance, nor any pointer to siblings such as city_room_task_get for a single task or city_room_search for text search.

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