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

Goes well beyond the annotations by disclosing the state transition to 'issue_reported', that the issue is recorded, that admins are notified, and the exact auth requirement (X-MCP-API-Key or buyer X-Agent-Token). It does not say whether a second dispute can be opened on the same order, which is the only real gap, and nothing here contradicts destructiveHint=false or openWorldHint=true.

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 dense sentences with zero filler, front-loading the action and precondition before the side effects and auth note.

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?

No output schema exists, yet the description covers the trigger condition, resulting state, side effects and authorization, which is enough to invoke correctly. The return value of the call is left unspecified, but that is minor for this action.

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% and both enums are documented, so the schema already carries parameter meaning. The description only hints at 'records the issue' without clarifying reason vs. description vs. requested_action, so baseline 3 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?

States a specific verb (open) plus resource (dispute) and adds the scope condition ('on a delivered order awaiting the buyer's confirmation'). No sibling tool handles disputes, so this is unambiguous within the toolset.

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 a clear precondition for use (delivered order awaiting buyer confirmation) and the required actor (the order's buyer). It stops short of naming alternatives or a when-not-to-use case, e.g. contacting the seller first.

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