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

Annotations already declare readOnly, idempotent, non-destructive and closed-world, so the safety bar is low; the description still adds real behavior: it returns procedural guidance, performs no browsing on its own, and explains the rationale (no public DistroKid API, no official MCP server). It does not describe what happens if no Cloud Browser session exists, which is the main remaining behavioral gap.

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?

Short and front-loaded, with the key surprise (it returns instructions, not data) placed before the follow-up action. Minor waste: 'from ChatGPT, Claude or any AI agent' is filler, and 'DistroKid's official API:' is a dangling fragment before the real statement about no public API.

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 tool the description is close to sufficient: it says what comes back, that nothing is clicked, and which tools execute the plan. It would be complete at 5 with a note on prerequisites (the Cloud Browser session / signed-in DistroKid account) required before the follow-up browser calls can succeed.

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, which is the baseline-4 case; there are no arguments whose meaning could be lost. The description appropriately spends no words on nonexistent inputs.

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 ('Get HyperFollow stats') and then corrects a likely misread by disclosing that the tool actually returns step-by-step instructions (screens, buttons, fields) rather than the stats themselves. It is distinguishable from siblings such as distrokid_get_daily_stats or distrokid_get_earnings_by_store by the HyperFollow resource, though it never names those siblings explicitly.

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?

Explicitly frames itself as the first half of a two-step workflow: run this to learn the steps, then perform them with cotlet_browser_* in the user's DistroKid Cloud Browser, and states it 'opens nothing by itself.' That is clear when-to-use guidance with a named alternative. It lacks an explicit when-not / comparison against the other distrokid_* read tools.

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