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

Annotations only declare readOnlyHint=false; the description meaningfully adds the admission workflow prerequisite (enroll then bind_actor), which is behavioral context the schema doesn't carry. It still omits what state changes, whether the challenge is reversible, and the response shape, so it only partially covers the burden.

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?

Only two short fragments, so it is compact and front-loads the admission requirement. The bracketed tag plus a terse, cryptic assertion make it read like an internal note rather than a polish, costing structural clarity.

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 mutation tool (readOnlyHint=false) with no output schema, the description should say what raising a challenge actually does and what results from it. It covers the admission prerequisite but leaves the operation's effect and success conditions ambiguous, which is a significant gap for an agent deciding whether to invoke it.

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 matter_id and actor_token are already fully documented in the schema. The description adds nothing about parameter syntax or format, so the baseline 3 for a fully-covered schema applies.

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?

The title 'Raise challenge' is a verb+resource, but the description only states a constraint ('A worker cannot write the disposition by challenging into a verdict') rather than a positive statement of what raising a challenge does. An agent learns what the tool is NOT for, but not what effect it produces, so the definition stays close to a tautology of the 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?

It provides a real precondition ('NEEDS ADMISSION: enroll, then atlas.bind_actor') and an implied exclusion (not for writing a disposition), which is more than nothing. However, it never states the positive situation in which this tool should be chosen over siblings like atlas.room_act or atlas.request_review.

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