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, and the description is consistent with them by stating it 'opens nothing by itself' and takes no side effects. It adds genuine context beyond the annotations: what the return contains (screens, buttons, fields) and that a Cloud Browser session is required to actually complete the task.

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 behavior and the handoff to browser tools are front-loaded in the first two clauses. The trailing note about Skiddle's official API being in beta, non-commercial, and lacking an MCP server is somewhat tangential but does justify why a guided-browser approach is used instead of an API call.

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, and the description compensates by explaining that the return is step-by-step instructions. For a zero-parameter, read-only guide tool this is nearly complete; the only minor gap is that it doesn't state what the agent should do if no Skiddle Cloud Browser session exists yet.

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; the baseline for a 0-param tool applies. The description doesn't imply any hidden inputs, which keeps it consistent with the empty schema.

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 (add guests to the guestlist in the user's own Skiddle account) and then clarifies the actual mechanic: it returns step-by-step instructions rather than performing the action ('opens nothing by itself'). That clarification is essential because the name would otherwise imply an action, and it also separates this tool from the cotlet_browser_* primitives it hands off to.

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 states the execution path explicitly: use this first, then perform the steps with cotlet_browser_* in the user's Skiddle Cloud Browser. It doesn't explicitly state when NOT to use it (e.g., when the user already has the screen open), but the sequencing guidance is clear enough to route an agent correctly.

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