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

Adds real context beyond the annotations: it discloses that it opens nothing by itself and only returns procedural guidance, which is exactly the side-effect profile an agent needs. The note that Kahunas publishes no API docs explains why the browser tools are required. Annotations (readOnly, idempotent, non-destructive) are consistent rather than contradicted.

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 behavioral fact (returns steps, opens nothing) is front-loaded, but the second sentence is overloaded and the third is a grammatical fragment ('Kahunas's official API: Kahunas publishes no API docs.'). Minor tightening would make the routing instruction easier to scan.

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 parameters, no output schema, and annotations covering safety, the description supplies what remains: what it returns (screens, buttons, fields) and how to continue with browser tools. Little is missing for a zero-argument guide tool.

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 schema burden is nil and the baseline is 4. Nothing in the description is needed to disambiguate inputs, and none is claimed.

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?

Names a specific verb and resource (list check-ins in the user's Kahunas account) and immediately clarifies the actual output is a step-by-step how-to rather than data. The slight tension between the name 'list' and the guide-style return is resolved by the second sentence, but an agent skimming only the first clause could still expect retrieved records.

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?

Explicitly routes follow-up work to the cotlet_browser_* tools in the user's Kahunas Cloud Browser, which tells the agent what to do after this call. It does not state when-not to use it versus kahunas_list_clients or cotlet_app_guide, so there is no exclusion guidance.

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