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 with that, actively reinforcing it ('opens nothing by itself'). It also discloses the return shape at a high level (screens, buttons, fields) and the required follow-up execution path, which is genuinely additive beyond the structured fields. The trailing API/OAuth background is context rather than behavior, so it is not a full 5.

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 'opens nothing' caveat are front-loaded, which is correct ordering. The closing sentence about Simpro's REST API, OAuth 2.0, absence of an MCP server, and a 'checked 17 Oct 2026' date is background that does not help an agent decide or invoke; trimming it would tighten the definition.

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 read-only annotations, the description covers the essential behavior and the hand-off to browser tools. The gap is the missing explanation of implicit context: how the target quote is determined (open tab, prior lookup, list_jobs/search results) is never stated, which an agent needs in order to sequence calls correctly.

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?

Zero parameters and an empty schema, so there are no parameter semantics to explain; the baseline of 4 applies. However, the description never addresses how the tool identifies which quote is being converted, which is the obvious question raised by a 0-parameter signature.

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 action and object: it produces step-by-step instructions for converting a quote to a job in Simpro, and explicitly clarifies it 'opens nothing by itself'. That last clause is essential because the tool name reads like a mutation. It does not name a sibling alternative, but it does name the follow-on tool family (cotlet_browser_*), which removes most ambiguity.

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 a clear workflow: call this first to get the screens/buttons/fields, then perform the steps with the cotlet_browser_* tools in the Cloud Browser. It never states when NOT to use it or what happens if the quote is already a job, so it falls short of full explicit exclusion guidance.

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