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

Annotations already declare readOnlyHint=true and destructiveHint=false; the description reinforces this with 'opens nothing by itself', which resolves the apparent conflict between the 'send' name and a read-only tool. It also discloses the return content (screens, buttons, fields) and the absence of a Tradify API, developer docs or webhooks — context not available in any structured field.

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 purpose is front-loaded, but the second sentence is a long chain of clauses ('Returns how to do it ... and opens nothing by itself; then do it with ...') that is harder to parse than necessary. The dated API-verification note ('checked 11 Oct 2026') is marginally useful but adds bulk.

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, it covers what is returned, what is not performed, and which tool family completes the action. The main omission is any note about the cotlet_apps/app-connection prerequisite before the browser steps are useful.

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?

There are zero parameters and the schema is fully closed (additionalProperties=false), so the baseline is 4. The description adds nothing about inputs, but there is nothing to add.

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?

States a specific verb and resource ('Send invoice in the user's own Tradify account') and then precisely reframes what the tool actually does: it returns step-by-step instructions rather than performing the send. It does not name the sibling 'send_invoice' or 'cotlet_app_guide', so the reader must infer the distinction from the cotlet_browser_* reference.

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 a clear follow-on action ('then do it with the cotlet_browser_* tools in the user's Tradify Cloud Browser'), which is real usage guidance. However, it never states when to pick this over the sibling 'send_invoice' or 'cotlet_app_guide', nor any prerequisite such as the user having Tradify connected.

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