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

The annotations already declare readOnlyHint=true, idempotentHint=true, and destructiveHint=false, and the description's 'opens nothing by itself' is consistent with them and genuinely useful because it tells the agent the tool is inert. Beyond that, the description adds mostly off-topic detail about PestPac's paid REST API rather than behavior of this call (no mention of what the instructions look like, 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 useful content is one sentence ('returns how to do it step by step... opens nothing by itself; then do it with cotlet_browser_*'). It is padded with marketing framing ('from ChatGPT, Claude or any AI agent') and a long tangent about PestPac's API setup fee and per-call pricing with an odd future date, which does not help an agent decide or invoke.

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 no-parameter, no-output-schema guidance tool, the description covers the essentials: what it returns (screens, buttons, fields), that it performs no action itself, and which tools to use next. Only minor gaps remain, such as what happens if the user has no PestPac cloud browser session.

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 and the schema coverage is 100%, so per the baseline this scores a 4. There is nothing parameter-wise the description could add, and it correctly implies no inputs are needed.

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 resource (unpaid invoices in the user's PestPac account) but immediately reframes the tool's actual behavior as returning step-by-step instructions rather than listing data, so the name and the behavior pull in different directions. The clarification is present, but an agent scanning names could reasonably expect a data-returning list tool. No sibling PestPac tool is named or contrasted.

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 downstream workflow: get the steps here, then execute them with the cotlet_browser_* tools in the user's PestPac Cloud Browser. That is useful implied sequencing, but there is no explicit when-not guidance and no named alternative among the pestpac_* siblings, so the agent must infer selection rules.

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