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

Annotations already declare readOnlyHint=true, and the description reinforces this with the concrete clarification that it 'opens nothing by itself', removing the risk of an agent assuming the invoice gets created. It adds useful non-obvious context about the handoff to the Cloud Browser and the API being off by default, though it doesn't describe the shape or length of the returned instructions.

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 purpose and the 'opens nothing by itself' clarification are front-loaded, which is the right structure. But phrases like 'from ChatGPT, Claude or any AI agent' are filler, and the trailing API sentence is a convoluted fragment with an oddly specific date that doesn't directly help an agent invoke the tool.

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 description covers what an agent needs: what it returns (screens, buttons, fields), that it is non-mutating, and what to use next. It stops short of stating prerequisites such as an available Cloud Browser session or what the guide looks like when the user's plan differs.

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 per the baseline this is a 4. The description's note that the tool is scoped to 'the user's own AroFlo account' usefully implies the implicit account/session context that stands in for parameters.

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 action and resource (create a final invoice in the user's AroFlo account) and explicitly resolves the tension in the name by stating it returns step-by-step AroFlo instructions rather than performing the action. It also identifies the actual execution path (cotlet_browser_* tools), so an agent can tell what it gets from this tool versus the browser siblings.

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 two-step workflow context — call this to get the steps, then act via cotlet_browser_* in the AroFlo Cloud Browser — and implies the API is not a viable route because it is disabled by default. However, it never states when NOT to use it, nor does it distinguish it from other invoice-related siblings such as aroflo_approve_invoice or aroflo_email_invoice.

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