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

Annotations already declare readOnly, idempotent, non-destructive and closed-world, so the safety profile is covered. The description still adds real value beyond them by stating the tool performs no action and opens nothing by itself, and by explaining the API situation (no documented API; QuickBooks the only named integration), which tells the agent why a browser path is required. It does not describe 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 operative instruction (returns steps, acts via cotlet_browser_*) is reasonably front-loaded, but the opening sentence is a fragment and the closing API/404 narrative is verbose for what it contributes. Roughly a third of the text is investigative backstory rather than call-shaping information.

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, output-schema-less helper, the description covers what it returns (step-by-step screens, buttons, fields), what it does not do, and the follow-up tooling. Complete enough to call correctly, though a one-line statement of what 'activity' means here would close the last 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 with 100% schema coverage, so there is nothing for the description to disambiguate. No parameter-level gap exists.

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 never plainly says what the tool IS; 'Activity in the user's own EZ Lawn Biller account' is a fragment that echoes the name and title. It only indirectly reveals the real function through 'Returns how to do it in EZ Lawn Biller step by step (screens, buttons, fields)', which suggests a how-to/knowledge lookup rather than the activity-log data a sibling ('ez_lawn_biller_activity_log') implies. The verb+resource pairing is present but buried behind ambiguous framing.

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?

It gives clear sequencing guidance: call this first to learn the step-by-step procedure, then 'do it with the cotlet_browser_* tools in the user's EZ Lawn Biller Cloud Browser'. It also implicitly excludes itself from performing actions ('opens nothing by itself'). It does not explicitly distinguish itself from ez_lawn_biller_activity_log or other siblings, so it stops short of a 5.

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