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

Annotations already declare readOnlyHint=true, idempotentHint=true and destructiveHint=false; the description is consistent with that and adds the key behavioral fact that it 'opens nothing by itself,' preventing an agent from assuming a browser session is launched. It also discloses that the return value is procedural guidance plus an API availability note. It does not describe the shape or length of the returned steps, which would have made it a 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 core message is front-loaded in the first sentence, but the text is padded by repeating the '(lexoffice)' gloss four times and by an oddly specific 'checked 14 Oct 2026' parenthetical that adds little for an agent deciding whether to call it. The three-sentence structure is serviceable but not tight.

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 output schema, the description correctly compensates by explaining what is returned — step-by-step screens, buttons and fields — and what must happen next via the browser tools. For a zero-parameter, read-only guidance tool this is close to sufficient; only the absence of any detail on the returned content's extent keeps it from a 5.

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 of 4 applies. The description correctly implies no inputs are needed, and the schema confirms an empty object with additionalProperties false. There is no parameter meaning left unstated.

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 verb and resource ('Create invoice in the user's own Lexware Office account') and then clarifies the actual deliverable: a step-by-step how-to rather than the mutation itself. That clarification is essential because the tool name implies it performs the creation, but it is stated only after the misleading opening clause. An agent can determine what it gets back, though the phrasing requires careful reading to avoid assuming the invoice is actually created.

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 follow-on path — use the cotlet_browser_* tools in the Cloud Browser to actually perform the steps — which is real guidance about sequencing. However, it never distinguishes this from sibling tools such as lexware_office_create_quote or lexware_office_finalise_invoice, nor does it say when this guide-first approach is preferable to a direct API-style action. Usage is implied rather than scoped against alternatives.

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