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

Annotations already declare readOnlyHint, idempotentHint, destructiveHint=false and openWorldHint=false, so the safety profile is covered structurally. The description reinforces that with "opens nothing by itself" and adds the valuable disclosure that the output is procedural guidance rather than data. Beyond that it says nothing about the shape, length, or reliability of the returned steps, so it adds only modest context over the annotations.

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?

Three tight sentences with the action front-loaded, then the return value, then the handoff to browser tools. The trailing fragment "Acumatica's official API: Yes." is terse but adds a relevant fact without padding the description.

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, no output schema, and rich annotations, the description covers what an agent needs: what it returns, that it is non-mutating, and which tools to use next. It could say more about what the step-by-step output contains or how granular it is, but nothing essential for correct invocation is missing.

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 nothing for the description to disambiguate and the baseline of 4 applies. The description correctly signals that no scoping arguments exist by framing the target as "the user's own Acumatica account."

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?

States a specific verb and resource ("List open invoices in the user's own Acumatica account") and immediately corrects the likely misreading by saying it "Returns how to do it in Acumatica step by step (screens, buttons, fields)." The name/behavior tension (it does not return invoice data itself) is resolved, but only after the reader gets past a potentially misleading first sentence.

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?

Explicitly routes the follow-up work to "the cotlet_browser_* tools in the user's Acumatica Cloud Browser" and states this tool "opens nothing by itself," which is clear context for sequencing. It does not name any exclusion case where a direct Acumatica API tool should be preferred instead, so it stops short of full when/when-not guidance.

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