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

The readOnlyHint, idempotentHint, destructiveHint=false and openWorldHint=false annotations already declare the safety profile, and the description is fully consistent with them by stating the tool opens nothing on its own. It adds genuine context beyond the annotations by explaining that no public EZ Lawn Biller API exists, which justifies why browser automation is required. The main omission is any hint about the shape 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 hand-off to browser tools come first, which is the right ordering. There is minor filler in the 'from ChatGPT, Claude or any AI agent' clause, and the dated API-audit sentence is verbose but does earn its place by explaining why no API path is offered.

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 parameterless, read-only guidance tool with no output schema, the description covers everything an agent needs: what it returns, that it has no side effects, and which tools to use next. The absence of any indication of the instruction payload's granularity or scope (e.g., which billing scenarios are covered) is the only remaining gap.

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 no parameter meaning for the description to carry; baseline 4 applies. The description correctly implies no inputs are needed by framing the call as a self-contained request for guidance.

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 task (one-off billing) and, crucially, states what the tool actually produces: step-by-step instructions covering screens, buttons, and fields. It also draws a clear boundary between itself and the action-taking siblings by saying it 'opens nothing by itself' and that execution happens via cotlet_browser_* tools. It does not explicitly differentiate against close siblings like ez_lawn_biller_new_one_time_service or ez_lawn_biller_edit_one_time_service, keeping it short of a 5.

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?

Usage is spelled out: call this to learn how one-off billing is done, then perform it with the cotlet_browser_* tools in the user's Cloud Browser. The negative guidance ('opens nothing by itself') prevents an agent from expecting an action. It stops short of naming which sibling to use for related billing tasks such as recurring or held billing, so alternatives are implied rather than enumerated.

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