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

Annotations already declare readOnlyHint=true, destructiveHint=false and idempotentHint=true, and the description is consistent with them by stating the tool 'opens nothing by itself'. It adds useful context that execution must happen through the cotlet_browser_* tools inside the user's Eventbrite Cloud Browser. However, it never explains what the returned instructions actually look like in structure, nor that it cannot target a specific order (having zero parameters) — a behavioral gap an agent would want closed.

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 core instruction is front-loaded and the 'opens nothing by itself' clarification earns its place. The final sentence about Eventbrite's public REST API, its lack of an MCP server, and a dated 'checked 5 Nov 2026' aside is irrelevant filler that does not help an agent invoke this tool. The middle sentence is also denser than it needs to be.

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 zero-parameter, no-output-schema guidance tool, the description adequately covers what comes back ('step by step screens, buttons, fields') and how to act on it. What is missing is the mismatch between a parameterless tool and the order-specific task it is named for, plus any note on the shape of the returned steps. Without annotations this would be weaker; with them, a 3 is fair.

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?

The tool takes zero parameters, which sets the baseline at 4 under the rubric. It drops to 3 because a refund-oriented tool with no order identifier is a semantic hole the description never addresses: nothing says whether the guidance is generic or whether the agent must supply the order context itself when it later drives the browser tools.

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 names a specific verb and resource ('Refund order in the user's own Eventbrite account') and immediately clarifies the actual deliverable: 'Returns how to do it in Eventbrite step by step (screens, buttons, fields)'. This corrects the misleading imperative name/title by telling the agent it produces instructions rather than performing the mutation. It falls short of a 5 because the headline phrasing still frames the tool as the refund action itself, which requires the reader to reconcile name against body text.

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 gives an explicit two-step workflow: call this to get the procedure, then 'do it with the cotlet_browser_* tools in the user's Eventbrite Cloud Browser'. That is genuine routing guidance toward specific sibling tools. It does not state when NOT to use it, nor distinguish it from other Eventbrite siblings like eventbrite_list_orders, which would be needed for a 5.

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