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

Goes well beyond the annotations by disclosing the state machine (claimed to in_review), that the claim is cleared and the token invalidated, that submission is irreversible and only the host can return the task, that no earlier result exists to replace, that evidence is untrusted text, and that other members observe the change. Annotations already flag destructive/non-idempotent, but the description adds substantial operational detail.

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 action and its target, then layers the state transition, token invalidation, irreversibility, and trust caveat. It is information-dense but every sentence contributes; only slightly verbose in stacking multiple caveats.

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 complex mutation with a nested evidence object and an existing output schema, the description covers everything an agent needs: when it applies, the state transition, token invalidation, undo limitations, and the trust status of evidence. Return values are handled by the output schema, so no gap remains.

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 100%, so the schema already documents room_id, task_id, claim_token, and the nested evidence object with kind/ref/revision. The description adds only that evidence is bound to a revision and carried with the claim token, which is marginal over the schema. Baseline 3 is appropriate.

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 ('Submit your work on a task you claimed, for the host's review') with the exact state transition (claimed to in_review). This clearly distinguishes it from siblings like city_room_task_claim, city_room_task_release, and city_room_task_renew, which operate on the claim rather than submitting a result.

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 clear context for use: on a task you have already claimed, with the claim token, for the host's review. It also notes the consequence that renew/release no longer apply once submitted, which frames the timing. It does not explicitly name a sibling alternative for the submission path, but the workflow context is strong.

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