ep_appeal_dispute

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

With no annotations, the description should fully disclose behavioral traits. It mentions preconditions for using the tool (participant, specific states) but does not describe side effects, whether the appeal modifies state, or what happens after invocation. The quote about trust is poetic but adds no operational transparency.

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?

The description is concise with two sentences and a quote. The first sentence clearly states the purpose, and the second adds conditions. The quote, while non-informative, does not significantly harm conciseness. Could be slightly tighter by omitting the quote.

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?

Given the complexity (3 parameters, one optional object, no output schema), the description lacks details about return value, side effects, or process after appeal. It does not explain what happens upon execution, leaving the agent underinformed about the tool's behavior.

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 schema already describes each parameter. The description adds no extra meaning beyond what the schema provides for dispute_id, reason, or evidence. Baseline score of 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?

The description clearly states 'Appeal a dispute resolution', specifying the action (appeal), the resource (dispute resolution), and adds eligibility conditions (dispute participants only, specific dispute states). This distinguishes it from siblings like ep_dispute_file and ep_dispute_status, which deal with initial filing and status checking respectively.

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 description gives explicit prerequisites: who can appeal (participants) and the required dispute states (upheld, reversed, or dismissed). However, it does not mention when not to use the tool or suggest alternatives, slightly reducing clarity.

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