Batch Get Mapbox Documents Tool

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

Beyond annotations (readOnlyHint, idempotentHint), the description reveals critical behavior: partial failures are handled gracefully—failed pages return error messages instead of failing the whole batch. This adds significant value for an agent deciding how to handle errors.

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?

Two terse sentences that pack maximum information: purpose, efficiency comparison, batch limit, and return behavior. No wasted words; each sentence earns its place.

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 no output schema, the description adequately explains return format (array of results with error messages on failure). Combined with annotations and input schema, it covers all behavioral aspects needed for safe and effective use.

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?

Although schema coverage is 100%, the description adds the important constraint that all URLs must be mapbox.com URLs, which is not enforced by the schema's format: uri. This domain restriction is essential for correct usage and goes beyond what the schema provides.

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?

Description clearly states 'Fetch the full content of multiple Mapbox documentation pages' with a specific verb and resource. It distinguishes itself from sibling get_document_tool by noting efficiency and from search_mapbox_docs_tool by focusing on fetching full content rather than searching.

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 states 'More efficient than calling get_document_tool multiple times,' directly guiding the agent to prefer this tool for batch requests. Also sets a clear limit (max 20) and mentions return behavior, leaving no ambiguity about appropriate use cases.

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