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 profile is covered. The description adds value beyond that: the response is markdown, long pages are split into parts with an offset to continue from, and no authentication is required. It does not mention rate limits or truncation limits, but the operational behavior an agent needs is present.

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?

Four short sentences, front-loaded with the action and format, then input forms, then pagination, then the auth note. Each sentence supplies distinct operational information with no filler or repetition.

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 must carry the return-shape burden, and it does: markdown, possibly paginated in parts. Combined with annotation coverage and fully described parameters, an agent has everything needed to call this correctly and continue on long pages.

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 coverage is 100%, so baseline would be 3, but the description adds meaning the schema lacks: it explains where a full URL legitimately comes from (a `Source:` line) and that the `offset` value to use is the one reported at the end of a prior response. That is real semantic guidance about parameter provenance rather than restatement.

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 ('Read a page of docs.dodopayments.com') and the return format ('as markdown'), which cleanly separates it from search_docs in the sibling set. An agent knows immediately this fetches content rather than locating it.

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?

Gives concrete invocation guidance: pass a docs path like `/developer-resources/webhooks` or a full URL taken from a `Source:` line, which implicitly routes the agent here after a search result. It also tells the agent to re-call with `offset` for long pages. It stops short of explicitly naming search_docs as the alternative for discovery, so it is clear context rather than full when/when-not routing.

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