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

Annotations already establish readOnly=true, idempotent=true, openWorld=false, so the description is not obligated to restate safety. It does add genuinely non-obvious behavior: the tool performs no navigation ('opens nothing by itself') and its return value is procedural instructions listing screens, buttons, and fields. The note that Joy has no public API is useful contextual constraint that prevents an agent from hunting for an API route.

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 key fact—that this returns instructions rather than data—is stated in the first sentence, which is the right front-loading choice. The semicolon-chained clauses and the trailing API-policy note make the second half dense, but every element carries information an agent needs.

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, annotation-rich tool with no output schema, the description covers the important ground: what is returned (step-by-step instructions), what is not done (no browser opened), and what to do next (cotlet_browser_* tools). It stops short of specifying what the guide text actually looks like or whether the user must already have a linked Joy account, which would fully close the loop.

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 and the schema is a closed empty object, so there is nothing for the description to disambiguate. The baseline of 4 applies; no parameter-related meaning is missing or needed.

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 ('Get RSVP status in the user's own Joy account') and immediately clarifies the real output: a step-by-step guide, not the live RSVP data itself. That correction is important because the tool name alone would suggest it retrieves the status directly. It does not, however, differentiate itself from the sibling cotlet_app_guide, which appears to serve the same guide-generation role.

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 a workflow hint—'opens nothing by itself; then do it with the cotlet_browser_* tools in the user's Joy Cloud Browser'—which tells the agent this is a preparatory step in a two-phase flow. What is missing is any statement of when to prefer this over joy_list_guests, joy_get_call, or cotlet_app_guide, and no exclusions are given. Usage is therefore inferable but not explicitly routed.

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