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

Annotations already declare readOnlyHint=true, idempotentHint=true and destructiveHint=false, and the description reinforces this by stating it 'opens nothing by itself' and requires a browser session to execute. It also discloses the return shape (screens, buttons, fields), which annotations cannot convey. It stops short of saying what happens if no Simpro browser session is active.

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 core purpose and execution handoff are front-loaded in the first two sentences, but the trailing sentence about Simpro's REST API and OAuth 2.0 and the absence of an official MCP server is justification boilerplate that adds nothing to invocation decisions. Roughly a third of the text is expendable.

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 must explain what comes back, and it does (step-by-step screens, buttons, fields). Combined with the explicit pointer to cotlet_browser_* tools for execution, an agent has enough to call it correctly; the only gap is any precondition about an active Simpro browser session.

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 an empty object, so there is nothing for the description to disambiguate. Baseline for a no-parameter tool applies.

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 first sentence names a specific verb and resource ('Create quote in the user's own Simpro account') and the second immediately reframes the actual behavior ('Returns how to do it in Simpro step by step ... opens nothing by itself'). That reframing is essential, because the verb 'create' alone would imply the tool performs the write; the description corrects this but only after the initial framing, so an agent skimming the opening could misread it.

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 explicit follow-on routing: use the cotlet_browser_* tools in the user's Simpro Cloud Browser to actually perform the creation. It does not name or exclude sibling workflows such as simpro_convert_quote_to_job or simpro_list_jobs, but the guidance for the create flow itself is unambiguous and actionable.

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