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

Annotations already declare readOnlyHint=true, idempotentHint=true, destructiveHint=false and openWorldHint=false, so the safety profile is covered. The description adds real behavioral context beyond that: the return format is step-by-step guidance, nothing is opened or changed, and the actual work is delegated to browser tools. The note that no public EZ Lawn Biller API exists (404s on /api, /developers, /docs; QuickBooks named as the only integration) explains why browser automation is the only path, which is useful context for an agent. It does not describe response length or instruction structure in detail, so it is not a 5.

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 description is front-loaded and covers what the tool is, what it returns, what it does not do, and what to do next. Every sentence carries weight, including the API-availability note, which justifies the browser-based workflow. The single long sentence packing the API audit details is slightly dense, keeping it from a 5.

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 0-parameter, no-output-schema tool with rich annotations, the description supplies what an agent needs: the tool returns a step-by-step walkthrough, performs no action itself, and hands off execution to the cotlet_browser_* tools. It does not specify the exact return structure beyond 'screens, buttons, fields,' which is a minor gap rather than a blocking one.

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 has zero parameters, so there are no parameter semantics to explain. The baseline for a 0-parameter tool is 4, and nothing in the description detracts from that.

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 states a specific resource and action (add an Item in EZ Lawn Biller) and immediately clarifies that the tool returns step-by-step instructions (screens, buttons, fields) rather than performing the write. That clarification is essential because the name and title imply mutation, so an agent can still tell what this really does. It lacks explicit differentiation from sibling tools like ez_lawn_biller_edit_billing_item, which is why it is not 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?

The description tells the agent exactly what to do next: use the cotlet_browser_* tools in the user's EZ Lawn Biller Cloud Browser to actually perform the action. It also sets a clear boundary by stating that this tool 'opens nothing by itself.' What it lacks is any statement about when not to use it or how to choose between this and sibling how-to tools.

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