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

Annotations already declare readOnlyHint=true and destructiveHint=false, but the title implies a send action, so the description's explicit 'opens nothing by itself' is genuinely valuable disambiguation. The API 404 note explains why browser automation is required, though return format details beyond 'screens, buttons, fields' are not given.

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 and the execution path are front-loaded in the first two sentences, but the trailing paragraph about 404 responses from gymdesk.com/api and docs.gymdesk.com/api is verbose evidence-dumping that adds little for an agent deciding how to call the tool.

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 parameters, no output schema, and permissive annotations, the description covers what an agent needs: what it returns, that it performs no action, and where the real action happens. Only the absence of sibling-comparison guidance keeps it below complete.

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; baseline 4 applies. No misleading parameter claims are made.

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 clearly states this returns step-by-step instructions for sending a bulk SMS in Gymdesk rather than performing the send. It implicitly distinguishes itself from sibling messaging tools by calling out 'bulk text/SMS' and pointing to the browser tools for execution, though it never names a sibling alternative such as the targeted push or two-way message tools.

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 says to use cotlet_browser_* tools in the user's Gymdesk Cloud Browser to actually carry out the steps, which is useful routing. It does not state when to prefer this over sibling messaging tools, nor any exclusions or prerequisites (e.g. which Gymdesk plan supports SMS).

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