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

The key behavioral fact an agent needs — that this tool opens nothing by itself and only returns instructions (screens, buttons, fields) — is stated plainly and matches readOnlyHint=true and destructiveHint=false. It also discloses the absence of a public API, which explains why a browser-driving fallback is required. It does not describe the structure or length of the returned instructions.

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 behavior and the handoff to cotlet_browser_* tools come first, which is good. The trailing API-availability note (404s on /api, /developers, /docs, dated 11 Nov 2026) is tangential evidence that inflates the description without helping the agent call the tool.

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, read-only instruction-returning tool with no output schema, the description covers what matters: it does not act on its own, what it returns, and what the agent must do next. The only gap is that the shape of the returned steps is described only loosely.

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; baseline 4 applies. The description correctly implies no inputs are required by framing the call as a pure instruction lookup.

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 ("Pin notes in the user's own EZ Lawn Biller account") and immediately qualifies it: the tool returns step-by-step instructions rather than performing the pin. It does not explicitly differentiate itself from siblings like ez_lawn_biller_customer_notes or ez_lawn_biller_service_notes, so an agent must infer that those are distinct note types.

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?

Gives a clear operating context (user's own account, invoked from an AI agent) and an explicit next step: execute the returned steps with the cotlet_browser_* tools in the Cloud Browser. It stops short of stating when NOT to use it or how it relates to the sibling note tools.

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