List Mapbox Tokens Tool

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

Annotations already declare readOnlyHint, idempotentHint, and destructiveHint. The description adds significant behavioral context: secret token values are omitted for security, and pagination uses next_start field. These details go beyond the annotations, providing valuable transparency.

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 three sentences, each serving a purpose: stating the main action, explaining security behavior, and clarifying pagination mechanics. No redundant or unnecessary text.

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 tool's complexity (5 parameters, pagination, security nuance) and the presence of an output schema, the description covers all essential aspects: listing, filtering, pagination, and behavioral details. It is complete for an agent to correctly invoke the tool.

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?

All parameters are documented in the schema (100% coverage). The description adds specific insight into the start parameter's behavior (must come from previous response's next_start), which is not clear from the schema alone. This augmentation justifies above baseline.

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 the tool lists Mapbox access tokens for the authenticated user with optional filtering and pagination. It explains the distinction between public and secret token values, which adds specificity. This purpose is distinct from sibling tools like create_token_tool, making it unambiguous.

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?

The description mentions optional filtering and pagination, including crucial pagination guidance (start parameter from next_start). However, it does not explicitly state when to use this tool versus alternatives or when not to use it, though the listing context is clear.

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