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

Annotations already declare readOnlyHint, idempotentHint, and destructiveHint=false; the description reinforces this with 'opens nothing by itself,' confirming zero side effects. It goes further by disclosing the return content (screens, buttons, fields) and the API-token caveat, which is context annotations cannot carry. It does not mention whether guidance varies by RazorSync plan or version, so a four rather than a five.

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 most decision-relevant fact – that this only returns instructions and opens nothing – is stated early, and the follow-up tool routing is equally front-loaded. The trailing sentence about RazorSync's official API is longer than necessary and slightly tangential, though it does justify the browser-based 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?

There is no output schema, so the description must describe the return value, and it does so concretely ('how to do it in RazorSync step by step (screens, buttons, fields)'). Combined with zero required parameters and rich annotations, an agent has enough to invoke it correctly; only minor gaps around version variance remain.

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 no parameter semantics to compensate for; the baseline for a 0-param schema is 4. No parameter-related claims are made or needed.

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 names a specific task (sending an invoice in RazorSync) and crucially clarifies that the tool does not perform it but returns step-by-step instructions covering screens, buttons, and fields. The name 'send_invoice' would otherwise imply a write action, so this correction is valuable. It stops short of a five because the clarifying clause arrives after the imperative-sounding opening sentence.

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 explicitly routes the agent onward: 'then do it with the cotlet_browser_* tools in the user's RazorSync Cloud Browser,' which names the alternative tool family and the sequencing. It also notes the official RazorSync API exists but requires a support-issued token, implicitly explaining why the browser route is used. No explicit when-not-to-use case is stated, keeping it below a five.

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