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

Annotations declare readOnlyHint=true and destructiveHint=false, and the description corroborates this with 'opens nothing by itself,' so there is no contradiction. It adds context the annotations cannot express: that no official public API exists, so the work must go through the cloud browser. It does not describe what the returned steps look like or what happens if no browser session is open, which keeps it from 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 behavior is front-loaded, but the sentence bundles purpose, return format, execution path, and an API-availability aside into one long chain. The API note ('checked 8 Nov 2026') is defensible as justification for the browser fallback, yet it reads as reference material rather than operative instruction. A tighter split would make the actionable part easier to parse.

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 tool, the essentials are covered: what it returns, that it performs no side effects, and which tools carry out the action. The gap is that an agent does not learn what a successful response contains or whether prerequisite setup (an open Invoice2go cloud browser session, authentication) is needed.

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. There is nothing for the description to clarify beyond the empty schema, and the schema is fully closed (additionalProperties: false).

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 ('estimate in the user's own Invoice2go account') and immediately clarifies a non-obvious truth: it returns step-by-step instructions ('screens, buttons, fields') rather than creating anything. That disclosure is valuable because the tool name implies a write operation. It falls short of 5 only because the name/behavior mismatch requires the agent to read the whole first sentence to understand the tool is a guide, not an actor.

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: get the steps here, then execute them with the cotlet_browser_* tools in the Invoice2go Cloud Browser. That is a clear when-to-use and what-to-use-next statement. It does not name a case where this tool should be skipped (e.g. if a direct API existed), but the no-API note effectively closes that door.

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