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

Although the annotations already declare readOnlyHint=true, idempotentHint=true, destructiveHint=false, and openWorldHint=false, the description explains the non-obvious behavior that makes those hints make sense: this tool opens nothing itself and returns human-readable screens, buttons, and fields, and the actual work must be done through cotlet_browser_* tools. It also discloses that no public API exists, justifying the browser-automation path, though it does not describe the format 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 description is front-loaded with the action and its key caveat, then the follow-up execution path. The final sentence on API research (dated 404 results, QuickBooks as the only integration) is longer than needed and could be compressed, but it does justify the browser-based approach.

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, no-output-schema guidance tool, the description covers what is returned (step-by-step screens/buttons/fields) and how to complete the task. A residual gap is that it never explains how the agent should convey which visit to add, given the tool accepts no input, so the agent must infer that detail from conversation context.

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?

With zero parameters and 100% schema coverage, there is nothing for the description to disambiguate. Baseline of 4 applies; the description correctly does not invent parameter details.

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 uses a clear verb and resource ('Add visit in the user's own EZ Lawn Biller account') and adds the crucial clarification that the tool returns step-by-step instructions rather than performing the addition. The 'add' versus 'edit'/'cancel' distinction from siblings is apparent from the name and phrasing, but no sibling is ever named, so differentiation is implicit rather than explicit.

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 the workflow context: use this to get the how-to, then execute with the cotlet_browser_* tools in the user's EZ Lawn Biller Cloud Browser. That is clear usage context, but there is no explicit when-not guidance and no named alternative (e.g., edit_visit or cancel_this_visit) for adjacent intents.

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