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

Annotations already declare readOnlyHint, idempotentHint, destructiveHint=false and openWorldHint=false. The description adds meaningful context beyond them: it performs no UI action, it only returns procedural text, and the actual execution must go through cotlet_browser_* tools. The note about the absence of a public API explains why browser automation is the path. It stops short of describing the response shape or scope limits of the returned steps.

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 key behavior is front-loaded, but the opening clause restates the title ('Catalog in the user's own EZ Lawn Biller account') rather than adding information, and the API-availability paragraph, while explanatory, is longer than needed. It is serviceable but not tight.

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 guidance tool with no output schema, the description covers what is returned (step-by-step screens, buttons, fields) and the follow-up path (cotlet_browser_* tools). The main remaining gap is that it does not clarify the scope of the catalog relative to the sibling service catalog.

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 the baseline is 4. Nothing in the schema needs elaboration, and the description correctly implies a parameterless 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?

The description states a specific outcome: it returns step-by-step instructions (screens, buttons, fields) for performing an action in EZ Lawn Biller, and explicitly 'opens nothing by itself'. That distinguishes it from the action-performing siblings. However, the resource itself is described only as 'Catalog', which is vague about what the catalog actually contains, and it is not distinguished from the similarly named ez_lawn_biller_service_catalog.

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?

There is an implied workflow: call this first to learn the steps, then execute them with the cotlet_browser_* tools in the Cloud Browser. That is useful routing guidance. But there is no explicit when-not-to-use guidance and no differentiation from the sibling catalog tool, so an agent must infer which catalog to call.

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