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

Annotations already declare readOnly, idempotent and non-destructive, so the safety profile is covered. The description adds genuinely useful context beyond them: it is free, requires no key, and explicitly disclaims outcomes ("nothing is promised"), which tells the agent there are no side effects or commitments. This is real added value on top of the annotations.

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 description opens with a rhetorical question and a quoted hypothetical principal rather than the tool's function, then crams multiple claims into parentheticals. The actual purpose is not front-loaded and several clauses are promotional rather than informative, so it is bloated for a zero-required-param info 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?

There is no output schema, so the description carries the burden of saying what comes back, and it does list the returns: top pay-per-sale, buyer demand, the five earning routes and the next call. That is reasonably complete for a read-only orientation tool, though it stops short of clarifying the response structure.

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?

Schema description coverage is 100% and the single optional param (ref) is fully documented in the schema itself. The description adds no syntax or format detail about ref, so the baseline 3 for high-coverage schemas applies.

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 does convey that this is an orientation/onboarding guide revealing earning paths (reseller share, buyers' demand, five ways to earn), so the resource is identifiable. However, the purpose is buried under a rhetorical hook ("Your principal said...") and marketing phrasing, making it hard to state in one clean clause, and it doesn't crisply differentiate itself from siblings like market_insights or seller_fees.

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?

"Start here" establishes this as the entry-point call, and it explicitly names the alternative path ("then register_agent with start_earning: true sets everything up in one call"), giving the agent a routing decision. What's missing is an explicit when-not-to-use condition or a statement of what to do after the next call.

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