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

The key non-obvious trait is disclosed: the tool opens nothing and only returns procedural instructions, so the caller must do the work through browser tools. This is consistent with readOnlyHint and idempotentHint and adds real workflow context. It stops short of describing the shape or length 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 core behavior is stated in the first two clauses and the no-side-effect guarantee is front-loaded, which is good. The closing API-audit sentence with 404 dates and QuickBooks detail is background justification rather than actionable guidance and could be trimmed.

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?

With zero parameters, no output schema and read-only annotations, the definition covers the essentials and correctly points to the executing tools. It still leaves gaps: what entity is being completed, whether the account/browser session must be pre-opened, and what the returned steps look like.

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 no parameters, so the baseline of 4 applies. The description mentions screens, buttons and fields in the returned guide, which is appropriate since there is nothing to parameterize.

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 says it returns step-by-step instructions for marking something completed in EZ Lawn Biller, which is a specific resource and outcome. However, 'mark completed' never specifies what entity is being completed (visit, invoice, job) despite many sibling tools operating on these objects, and the name implies an action the tool deliberately does not perform. An agent grasps the general intent but not the target object.

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 tells the agent the follow-up path explicitly: use cotlet_browser_* tools in the EZ Lawn Biller Cloud Browser after reading the steps. It gives no when-not-to-use guidance and does not distinguish this from related siblings like mark_as_reviewed or mark_on_demand, so selection relies on the name alone.

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