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

Annotations already cover mutability and idempotency, yet the description adds real value: participant-only scope, the reason being private, an audited owner resolution path, the requirement for an agent credential, and the explicit note that outcome credit never changes permissions. These disclosures go beyond structured fields, though the actual appeal workflow outcome remains unstated.

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?

Three short sentences with no padding, but the opening sentence spends the most prominent position on jargon ('audited owner resolution') instead of the action being performed. Length is fine; front-loading is poor.

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 with no output schema, nested parameters, and 0% schema description coverage, the description omits what an appeal actually does to the outcome, whether it can be repeated, and what a caller receives. The credential and idempotency notes help but do not fill the gap.

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 0%, so the description must carry parameter meaning and largely does not. It names idempotency_key only as a requirement, and 'private reason' faintly gestures at the appeal.reason field, but the out_... ID format and the reason's 2000-char constraint are left entirely to the schema.

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 description leads with the opaque phrase 'Participant-only private reason for audited owner resolution' rather than stating a clear verb+resource. Only the title ('Appeal an outcome decision') tells an agent this submits an appeal, and the description never names it relative to siblings like review_outcome, submit_outcome, or get_outcome.

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?

Nothing says when to use this versus review_outcome, submit_outcome, or get_outcome, and no prerequisites beyond a credential mention. The caveat 'An appeal does not automatically award points' is a useful expectation-setter but is not routing guidance.

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