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

Annotations already declare readOnlyHint=true and destructiveHint=false; the description adds real value beyond them by stating it "opens nothing by itself" and only returns the procedure, which resolves the ambiguity created by an action-style name like joy_add_guest. The note that Joy has no public API, developer program or Zapier app explains why the browser-tool chaining 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?

Front-loaded with the purpose, then the return shape, then the execution path — a logical order with no filler. The closing sentence about Joy's API status is somewhat tangential and carries an oddly precise date, but it does justify the browser-based approach.

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, no output schema and a read-only annotation profile, the description covers what the agent needs: what is returned (screens, buttons, fields) and what to do next. It does not address edge cases such as the user lacking a Joy account, which keeps it from a 5.

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 nothing for the description to disambiguate; baseline 4 applies. The description correctly implies no inputs are needed to obtain the guide.

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 ("Add guest in the user's own Joy account") and immediately clarifies the actual output is a step-by-step procedure rather than a mutation. It does not explicitly distinguish itself from joy_list_guests or cotlet_app_guide, but the mention of cotlet_browser_* as the execution path makes the role clear.

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 concrete usage context — callable "from ChatGPT, Claude or any AI agent" — and prescribes the follow-up: "then do it with the cotlet_browser_* tools in the user's Joy Cloud Browser." No explicit when-not-to-use or comparison to cotlet_app_guide, so it falls short of a 5.

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