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

Annotations already declare readOnlyHint, idempotentHint, openWorldHint and destructiveHint=false, so the safety profile is covered structurally. The description adds genuine workflow context beyond that: this is the follow-up step to a search, and it returns complete page content rather than snippets. It leaves out details like error behavior for non-docs URLs or the return format, which keeps it from a 5.

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?

Three short sentences with the core action front-loaded, followed by the sequencing guidance and the batch alternative. Every sentence carries distinct information and nothing is repeated from the schema or annotations.

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 single-parameter, read-only fetch with full annotation coverage, this covers the action, the workflow position, and the sibling selection. The only gap is that with no output schema, the description says 'full content' without hinting at the shape of the returned page, which an agent might want to know.

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 'url' parameter already documents the https://docs.mapbox.com constraint with an example. The description adds only the framing that the URL corresponds to a documentation page, so baseline 3 applies since the schema does the heavy lifting.

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 verb ('Fetch') and resource ('full content of a specific Mapbox documentation page') and scopes it by URL. It is clearly distinguishable from search_mapbox_docs_tool and batch_get_documents_tool, which it names 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?

It states exactly when to use it ('after search_mapbox_docs_tool to follow a link from the search results') and names the alternative for the excluded case ('For fetching multiple pages at once, use batch_get_documents_tool'). No inference is required.

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