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

Annotations already declare readOnlyHint=true, idempotentHint=true, destructiveHint=false, and the description is consistent with them by explicitly saying it 'opens nothing by itself' and that a separate browser tool does the writing. It adds the shape of the return (step-by-step screens, buttons, fields), which annotations cannot convey. However, 'Acumatica's official API: Yes.' is cryptic and conveys no actionable behavior, and prerequisites (connected account, open browser session) are unstated.

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 behavioral correction is front-loaded well, but 'from ChatGPT, Claude or any AI agent' is promotional filler and 'Acumatica's official API: Yes.' is a fragment that does not parse into useful information. Roughly a third of the text does not earn its place.

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 guide tool, the description covers what it returns and who executes the write, which is the minimum an agent needs. It omits prerequisites (an authenticated Acumatica session and an open Cloud Browser) and leaves the 'official API' claim unexplained, so it is adequate rather than complete.

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 there is no parameter meaning to add; the baseline for a 0-param schema is 4. The description correctly does not invent parameter discussion, though it also never explains how the target bill details get conveyed (presumably via the browser step).

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 AP bill in Acumatica) and then crucially corrects the name's implication by saying it 'Returns how to do it in Acumatica step by step (screens, buttons, fields) and opens nothing by itself.' That distinction is essential for an agent. It does not, however, differentiate itself from siblings like acumatica_create_ar_invoice beyond the AP/AR noun.

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 usage model: call this to get the procedure, then execute with cotlet_browser_* tools in the user's Acumatica Cloud Browser. That is real routing guidance to a sibling family. It stops short of stating when NOT to use it or what to do if the browser/account isn't connected.

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