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

Goes beyond the annotations by stating it opens nothing by itself and only returns screens, buttons and fields, which corroborates readOnlyHint and makes the read-only nature actionable. The note that AutoLeap's REST Partner API is gated and unavailable on Essentials/Pro/Elite explains why the browser path is used, though it reads more like product context than tool behavior.

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 surprising part (returns steps, opens nothing) in the first two clauses, then the execution path, then background. The API-gating sentence is the only borderline-extraneous element, but it prevents an agent from attempting the REST API instead.

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 and no output schema, the description correctly spends its space explaining what comes back (step-by-step screens, buttons, fields) and what does not happen. A note on what input context it keys off (e.g. which estimate it assumes) would close the remaining 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 zero parameters, so there is nothing for the description to disambiguate; the schema's additionalProperties:false already fixes the empty input. Baseline applies with no gaps.

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 (convert estimate to repair order) plus its scope, the user's own AutoLeap account. Crucially it also disambiguates the deliverable: it returns step-by-step instructions rather than performing the conversion, which separates it from cotlet_browser_* siblings and autoleap_send_estimate.

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 says this tool only produces the how-to and the actual work must be done with the cotlet_browser_* tools, which is clear routing guidance. It stops short of naming cotlet_app_guide as an alternative for general guidance or stating prerequisites such as needing an existing estimate, so the when-not branch is missing.

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