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

Annotations already declare readOnlyHint=true and destructiveHint=false, and the description usefully reconciles the misleading 'create' name by stating it 'opens nothing by itself' — so there is no contradiction, only clarification. It adds real context beyond the annotations (step-by-step output, no API/webhooks/Zapier, Xero add-on only, verification date), though it never states session/login requirements for the target browser.

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 behavior and handoff are front-loaded in the first two sentences, which is the important part. The closing paragraph on JobSheet's integration landscape earns its place as justification for browser automation, but the parenthetical trivia ('webhooks or Zapier app', 'checked 8 Nov 2026') adds length without changing agent behavior.

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 full annotation coverage, the description carries the burden of explaining what comes back — and it does ('step by step (screens, buttons, fields)'). It is nearly complete, missing only practical setup details such as whether the user must already be signed in to JobSheet before the browser handoff.

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 the baseline is 4 and there is no schema semantics the description needed to compensate for. Nothing about inputs is ambiguous because there are no inputs.

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 verb and resource ('Create invoice in the user's own JobSheet account') and immediately clarifies the actual mechanic: it 'Returns how to do it in JobSheet step by step (screens, buttons, fields)' rather than performing the action. That tells an agent exactly what it gets back and separates it from the browser siblings it later hands off to.

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, then 'do it with the cotlet_browser_* tools in the user's JobSheet Cloud Browser,' and it explains why (no public API, so browser automation is the only route). It stops short of explicitly naming when to prefer jobsheet_create_quote or jobsheet_create_job_sheet, but the resource distinction is self-evident.

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