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

Goes well beyond the readOnlyHint=true annotation by stating plainly that it 'opens nothing by itself' and that the browser actions happen later via cotlet_browser_* tools. It also explains why browser automation is needed (eDesk has a REST API but no MCP server), which preempts an agent's assumption that this tool mutates anything.

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-loads the action and the key caveat ('opens nothing by itself') in the first two sentences, which is the right ordering. The trailing note about eDesk's API is slightly tangential but earns its place by justifying the browser-tool handoff.

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, read-only guide with no output schema, it covers what the agent gets back (screens, buttons, fields) and what to do next. It could say more about prerequisites, such as the eDesk account needing an active Cloud Browser session, but the essentials are present.

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 baseline is 4; there is nothing for the description to disambiguate. It correctly avoids inventing parameter talk for an 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?

States a specific verb and resource (add an internal note in eDesk) and immediately clarifies the actual mechanics: it returns step-by-step instructions rather than performing the action. The distinction from the sibling edesk_reply_to_ticket (public reply vs internal note) is left implicit, so it falls just short of a 5.

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 a clear workflow: call this first to get the in-app steps, then execute them with the cotlet_browser_* tools in the eDesk Cloud Browser. It does not explicitly exclude alternatives such as replying to the customer or assigning an owner, but the context for use is unambiguous.

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