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

Annotations already declare readOnlyHint=true, openWorldHint=false, idempotentHint=true and destructiveHint=false, so the safety profile is covered. The description adds genuinely new context: it opens nothing by itself, it returns screen/button/field-level instructions, and Evite has no public API or official MCP server. That last point usefully explains why a browser-driven approach is required.

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 workflow is front-loaded and clear, but phrases like "from ChatGPT, Claude or any AI agent" and the dated API-check note ("checked 11 Oct 2026") are filler that dilutes the operative guidance. The sentence structure is serviceable but could be tightened.

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 no output schema, the description carries the burden of explaining return values, and it does so concretely (step-by-step screens, buttons, fields). Combined with the no-API rationale and the handoff to cotlet_browser_* tools, an agent has enough to call it correctly and know what to do next.

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 the baseline is 4. The description correctly implies no inputs are needed and focuses on what the call yields instead.

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 and resource ("Get RSVPs in the user's own Evite account") and clarifies the actual deliverable is step-by-step instructions rather than data. The name alone would mislead an agent into expecting RSVP data, but the description corrects that immediately. It distinguishes itself from the cotlet_browser_* siblings by naming them as the execution path.

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?

Explains the workflow: this tool returns instructions, then the agent should act with cotlet_browser_* tools in the user's Evite Cloud Browser. However, it gives no guidance on when to prefer this over other Evite siblings like evite_message_guests or evite_create_event, and no explicit when-not conditions.

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