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

Annotations already declare readOnlyHint, idempotentHint and destructiveHint=false, so safety is covered. The description adds non-obvious behavior: the call is free and starts no browser session, the default app is PestPac, and unknown apps degrade to a generic method rather than failing. That extra context justifies a 4 above the annotation baseline.

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 trigger sentence and the PestPac action list are front-loaded and every clause carries information. The first sentence is a dense colon-list that reads as a run-on, and the unsignposted jump from general scope to the PestPac enumeration makes skimming harder than it needs to be.

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 two-optional-parameter, read-only lookup with no output schema, the definition covers trigger, scope, fallback for uncataloged apps, cost, and supported actions. The remaining gap is minor: it does not clarify what the returned guidance looks like or whether an unknown app slug errors versus falling back.

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?

Schema coverage is 100%, so 'app' and 'task' are already documented as name-or-slug and free-text user intent. The description contributes beyond the schema by enumerating the PestPac actions covered (schedule/reschedule service order, list customers, list unpaid invoices, add customer note), which tells the agent what values of 'task' this guide actually supports.

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 enumerates exactly what the tool delivers: which browser to use for the workspace, the sign-in link, a step-by-step method, the app's screens/menus/actions, notes, and any dedicated tools. That is specific enough to separate it from the browser_* siblings, which perform actions rather than return guidance. It lacks an explicit leading verb such as 'Returns a guide', so the agent must infer the tool is a knowledge lookup rather than an operation.

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?

'Call it before the first browser step in an app' is an explicit, actionable trigger, and 'Works for any web app; one outside Cotlet's catalog gets the general method' sets the fallback expectation. It stops short of saying to prefer the pestpac_* dedicated tools over manual browser steps when both exist, which is the one routing decision an agent still has to make alone.

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