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

Annotations already declare readOnlyHint=true and destructiveHint=false; the description adds the crucial non-obvious behavior that the tool performs no side effect and only returns instructions, which explains why a "create" tool is read-only. It also supplies the rationale (Tradify publishes no API, developer docs or webhooks), which justifies the browser-automation path. Minor gap: it doesn't describe how detailed or structured the returned steps are beyond "screens, buttons, fields."

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 critical correction ("opens nothing by itself") is front-loaded, which is good. However, the final clause "Tradify's official API: Tradify publishes no API, developer docs or webhooks (checked 11 Oct 2026)" is awkwardly constructed with a dangling label and a dated verification stamp that reads as boilerplate rather than usable guidance.

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 no output schema and no parameters, the description carries the burden and largely meets it: it says what comes back (step-by-step screens, buttons, fields), what does not happen (nothing is opened), and what to do next (browser tools). An agent has enough to call it correctly; only the unexplored overlap with the sibling create_quote remains unaddressed.

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 there is nothing for the description to disambiguate; the baseline for a parameterless tool applies. Worth noting only that the absence of inputs is itself consistent with the claim that it merely returns guidance.

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 verb and resource ("Create quote in the user's own Tradify account") and immediately corrects the misleading name by clarifying it "Returns how to do it in Tradify step by step... and opens nothing by itself." That makes the real behavior unambiguous. It falls short of a 5 because it never explains how this differs from the sibling tool literally named create_quote, leaving the agent with two seemingly identical purposes.

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 explicit workflow guidance: call this first to get the screens/buttons/fields, then "do it with the cotlet_browser_* tools in the user's Tradify Cloud Browser." That handoff is concrete and names the alternative tool family. It stops short of stating when NOT to use it (e.g., when a direct API write tool is available) or why the sibling create_quote exists.

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