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

Annotations already declare readOnlyHint=true, destructiveHint=false, and idempotentHint=true; the description reinforces this by stating the tool 'opens nothing by itself.' It adds genuine context beyond the annotations: the return payload is procedural (screens, buttons, fields) and the official API alternative requires an AppSecretToken plus per-user AgreementGrantToken. It does not describe response length or failure modes.

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 the browser follow-up are front-loaded well, but the closing paragraph about e-conomic's REST API, AppSecretToken, and AgreementGrantToken is tangential to invoking this tool and adds noise. The single dense sentence packing 'Create... account from ChatGPT, Claude or any AI agent' is longer than it needs to be.

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 carries the burden of explaining what comes back, and it does so adequately ('returns how to do it step by step (screens, buttons, fields)'). Combined with the explicit pointer to the cotlet_browser_* execution path, an agent has enough to call it and act on the result. A note on how complete or account-specific those instructions are would close the remaining gap.

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 nothing for the description to disambiguate. No parameter information is needed or missing.

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 resource and outcome: it returns step-by-step instructions for creating a draft invoice in the user's e-conomic account, and explicitly says it 'opens nothing by itself.' This resolves the tension between the create-sounding name and the read-only nature. It does not explicitly distinguish itself from siblings like e_conomic_book_invoice or e_conomic_create_entry, which keeps it from a 5.

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?

Clear workflow guidance is given: get the instructions here, then execute them with the cotlet_browser_* tools in the e-conomic Cloud Browser. The API paragraph implicitly steers the agent away from a direct REST call by noting the developer-agreement/token prerequisite. There is no explicit 'do not use this when...' exclusion against the sibling e_conomic_* tools.

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