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

Annotations already declare readOnlyHint, idempotentHint, destructiveHint=false and openWorldHint=false, so the safety profile is covered. The description adds genuine value beyond that by stating it 'opens nothing by itself' and by describing the return content as screens, buttons and fields, plus why the browser path is needed (no MCP server for eDesk's REST API).

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?

Three sentences, front-loaded with what is returned and how to proceed, with no redundant restatement of the name. The closing note on eDesk's official API is slightly tangential but justifies the instruction-based, browser-driven 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 no input parameters and no output schema, the description carries the burden of explaining the return: it does so at a high level (screens, buttons, fields) and tells the agent what to do next. Exact output shape is unspecified, which is the only notable gap.

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 no parameters, so the baseline is 4; there is nothing for the description to disambiguate and it correctly implies a parameterless call.

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 states a specific resource (order and tracking in eDesk) and clarifies the non-obvious nature of the tool: it returns step-by-step instructions rather than the order data itself, which corrects the impression given by the name. It does not explicitly differentiate itself from sibling guide-style tools like cotlet_app_guide, keeping it 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?

It gives clear workflow context: call this first to get the procedure, then execute it with the cotlet_browser_* tools in the user's eDesk Cloud Browser. It does not name when-not-to-use conditions or alternatives among the edesk_* siblings, so exclusions are absent.

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