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

Annotations already declare readOnlyHint=true, idempotentHint=true, destructiveHint=false, and openWorldHint=false, so the safety profile is covered. The description adds genuinely non-obvious behavior: this tool returns an instructional guide rather than performing the action, and the real work must be delegated to cotlet_browser_* tools. That workflow disclosure is exactly the kind of context annotations cannot convey. Minor deduction for not describing the shape of the returned guide beyond 'screens, buttons, fields.'

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 purpose and the browser-delegation instruction are correctly front-loaded, but the trailing material about Eventbrite's v3 REST API, the absence of an Eventbrite-hosted MCP server, and a 'checked 5 Nov 2026' date does not help an agent decide or invoke. That trivia is roughly a third of the text and dilutes the operative guidance.

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?

With zero parameters and no output schema, the description must explain what comes back, and it does at a high level ('how to do it in Eventbrite step by step (screens, buttons, fields)') plus the required follow-up with browser tools. An agent has enough to call it correctly; only the precise return format is left implicit.

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, so there is no parameter semantics to explain and the schema is fully self-describing. Baseline 4 applies; the description neither helps nor harms here.

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 opening sentence gives a specific verb and resource with explicit scope: 'List events in the user's own Eventbrite account.' The 'own account' qualifier implicitly distinguishes it from eventbrite_search_public_events, but the later claim that Eventbrite has 'no public event search' muddies that contrast rather than sharpening it.

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 does usefully state the invocation model: it returns a step-by-step how-to and 'opens nothing by itself,' with the actual action to be carried out via cotlet_browser_* tools. However, it never names the sibling tools an agent should choose instead (eventbrite_list_orders, eventbrite_search_public_events, cotlet_app_guide), and the claim of 'no public event search' actively conflicts with the existence of eventbrite_search_public_events.

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