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

Annotations already declare readOnlyHint=true and destructiveHint=false, and the description is consistent, reinforcing that it "opens nothing by itself" and only returns guidance. It adds real context beyond the annotations by naming the follow-up tool family and the environment (Cloud Browser). The trailing "Help Scout's official API: Yes" is opaque and adds little verifiable meaning.

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 purpose and the no-side-effect guarantee are front-loaded, which is good. But the run-on second sentence mixes several ideas, and the dangling "Help Scout's official API: Yes." is cryptic enough to cost clarity without earning its place.

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 guidance tool with no output schema, the description covers what matters: what comes back (step-by-step screens/buttons/fields), that no action is taken, and which tools complete the task. It stops short of describing format or whether the output is conversation-specific, but nothing essential for correct invocation is missing.

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 empty, so the baseline is 4. The description adds nothing about parameters, but nothing is needed; it conveys the call is argument-free and returns instructional content.

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 makes the real behavior explicit: it "Returns how to do it in Help Scout step by step (screens, buttons, fields) and opens nothing by itself," which usefully corrects the impression created by the name 'add_note'. It does not, however, distinguish this from siblings like help_scout_reply_to_conversation or cotlet_app_guide, so an agent must infer which guidance tool fits.

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 clearly routes the workflow: call this first to get step-by-step instructions, then perform the action with cotlet_browser_* tools in the user's Help Scout Cloud Browser. What's missing is any exclusion or comparison — there is no statement of when NOT to use it versus the direct Help Scout API-style siblings or the generic app guide.

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