Get Mapbox Document Tool

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

Annotations already declare readOnlyHint, idempotentHint, etc., which the description does not contradict. The description adds that it fetches 'full content' but does not provide additional behavioral details like response format or potential limits. Given the strong annotations, this is adequate.

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 sentences, each serving a distinct purpose: stating the action, providing sequential usage, and noting an alternative. No filler, front-loaded with the primary function.

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?

Given the simple single-parameter schema and comprehensive annotations, the description adequately explains the tool's role and relationship to siblings. Does not cover error handling or output details, but for a fetch tool this is acceptable.

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% with the 'url' parameter having a clear description. The tool description adds no new meaning beyond 'by URL'. Baseline score of 3 applies as the schema already documents the parameter well.

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 clearly states 'Fetch the full content of a specific Mapbox documentation page by URL', with a specific verb and resource. It distinguishes itself from the sibling 'batch_get_documents_tool' by noting its role for single-page retrieval and references the sequential tool 'get_latest_mapbox_docs_tool'.

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 advises use after 'get_latest_mapbox_docs_tool' and contrasts with 'batch_get_documents_tool' for multiple pages, providing clear context. Missing explicit mention of when not to use (e.g., when searching), but still strong guidance.

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