Get Mapbox Document Tool

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

Annotations include readOnlyHint=true, openWorldHint=true, idempotentHint=true, and destructiveHint=false, which already disclose the safety profile. The description does not contradict these and adds minimal extra behavioral context (e.g., 'full content'), but it does not discuss potential side effects, rate limits, or output format. Since annotations lower the burden, a score of 3 is appropriate.

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 is two well-structured sentences. It front-loads the core function immediately, then provides usage context and an alternative in the second sentence. Every word contributes value with no redundancy.

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 tool with strong annotations, the description is largely complete. It states what the tool does, when to use it, and how it relates to sibling tools. It does not specify the exact return format (e.g., plain text, markup), but the absence of an output schema makes this a minor gap, so a 4 is warranted.

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 input schema already fully documents the 'url' parameter with format, example, and constraint. The description only echoes 'by URL' and adds no additional parameter-level semantics beyond what the schema provides. With 100% schema coverage, the baseline of 3 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 clearly states a specific action and resource: "Fetch the full content of a specific Mapbox documentation page by URL." It distinguishes from siblings by explicitly referencing get_latest_mapbox_docs_tool and batch_get_documents_tool, and the context signal for search_mapbox_docs_tool implies a different purpose.

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?

Explicit guidance is provided: "Use this after get_latest_mapbox_docs_tool to follow a link from the index" and "For fetching multiple pages at once, use batch_get_documents_tool instead." This clearly defines when to use and suggests an alternative, fulfilling the dimension well.

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