Place Details Tool

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

Annotations already declare readOnlyHint, idempotentHint, and non-destructive. The description adds value by listing specific details returned (photos, opening hours, ratings, phone numbers, website URLs) and mentioning attribute sets, providing behavioral context beyond annotations.

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 well-structured sentences: first states purpose, second provides usage guidelines. Every sentence earns its place, 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?

With output schema present, description need not detail return values. It covers prerequisites, usage flow, and available attribute sets, making it complete for a retrieval tool with multiple optional features.

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%, but description adds contextual meaning: mapbox_id 'obtained from search results', language affects place names/addresses, worldview for geopolitical sensitivity, and attribute_sets lists what each set includes. Enhances understanding beyond schema alone.

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 'Retrieve detailed information about a specific place using its Mapbox ID,' specifying the verb (retrieve) and resource (place details). It distinguishes from sibling search tools by indicating it is used after them to get additional details.

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 to use after search_and_geocode_tool, category_search_tool, or reverse_geocode_tool, and requires the mapbox_id field. Provides clear context for when to use this tool. No explicit when-not-to-use or alternatives, but sufficient given sibling list.

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