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

Annotations already declare readOnlyHint=true and destructiveHint=false; the description reinforces and explains that with 'opens nothing by itself', which is exactly the kind of clarification worth adding. The mention of ServiceTrade's REST API/OAuth2 and the absence of an official MCP server explains why this tool exists at all, though the '(checked 23 Oct 2026)' timestamp is incidental detail.

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-loaded with the key behavioral claim (returns instructions, opens nothing), followed by the workflow and then the rationale. The final API/docs sentence is longer than it needs to be for invocation purposes but does justify the tool's existence.

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, no-output-schema guidance tool, the description covers what it returns (screens, buttons, fields), that it has no side effects, and the next step. The only meaningful gap is disambiguation from servicetrade_create_quote.

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, so there is no parameter semantics for the description to carry; baseline 4 applies. The description correctly implies no inputs are needed by saying it just returns guidance.

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 gives a specific verb and resource ('Submit quote in the user's own ServiceTrade account') and immediately clarifies the actual behavior: it returns step-by-step instructions rather than performing the action. It does not, however, distinguish itself from the sibling servicetrade_create_quote, so an agent comparing the two 'quote' tools must guess.

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 states the follow-on workflow ('then do it with the cotlet_browser_* tools') and asserts it opens nothing itself, which is real when-to-use guidance. But it never says when to prefer this over servicetrade_create_quote, nor states prerequisites such as an open Cloud Browser session.

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