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

Strong beyond-annotation disclosure: it explicitly states the tool 'opens nothing by itself' and only returns how to do the task, which is the critical behavioral fact an agent needs given the 'add' naming. This coherently explains the readOnlyHint=true / destructiveHint=false annotations rather than contradicting them.

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 purpose and the browser-tool handoff are front-loaded and useful, but the trailing paragraph on PestPac's official API setup fee and call-based pricing is tangential to selecting or invoking this tool. That sentence does not earn its place in a definition this short.

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 that returns instructions, the description adequately conveys what comes back ('screens, buttons, fields') and what to do next. It could say more about the shape of the returned steps, but it is sufficient to call correctly.

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?

With zero parameters and a fully empty schema, there is nothing for the description to disambiguate; baseline applies. No misleading parameter claims are made.

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 and action (customer note in PestPac) and immediately clarifies the actual mechanism: it returns step-by-step instructions rather than performing the write. This resolves the tension between the verb 'add' and the read-only behavior, though the name still leans toward implying a mutation that an agent must read past.

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 workflow: call this to obtain the screens/buttons/fields, then execute with the cotlet_browser_* tools in the user's PestPac Cloud Browser. It does not explicitly state when NOT to use it or compare against the PestPac list/schedule siblings, but the sequencing guidance is concrete.

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