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

Annotations already declare readOnly, idempotent, non-destructive, closed-world. The description adds a genuinely useful trait beyond them: 'opens nothing by itself', i.e. invoking this has no side effects and produces only instructions, so the agent must follow up with browser tools. It does not say whether the guide assumes an already-open browser session or how it handles an unauthenticated state.

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 follow-up instruction are front-loaded, which is good. But 'from ChatGPT, Claude or any AI agent' is pure marketing filler, and the closing note on DistroKid's lack of an official API with a verification date is tangential to invoking this tool; the definition would be tighter without both.

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, read-only guide generator with no output schema, the description covers what it returns, that it has no side effects, and how execution proceeds afterward. The one real gap is the absence of a pointer to the sibling tool that retrieves actual earnings data, which an agent choosing among many distrokid_* siblings would benefit from.

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 and the schema is fully specified with additionalProperties false, so there is nothing for the description to disambiguate. Baseline of 4 applies; no parameter-level detail is needed or missing.

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 names a specific resource (earnings by store) and, crucially, states what the tool actually produces: a step-by-step guide with screens, buttons, and fields. That distinction matters because the name 'get_earnings_by_store' sounds like a data-fetch tool. It stops short of naming the sibling that actually returns earnings data (distrokid_list_earnings_rows), so the differentiation is implied 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?

There is a clear forward path — run this first, then execute the steps with the cotlet_browser_* tools in the DistroKid Cloud Browser. What is missing is when NOT to use it: an agent wanting raw earnings rows would plausibly land here instead of on distrokid_list_earnings_rows, and nothing steers it away.

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