ta_get_locations

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

Annotations already declare readOnlyHint and openWorldHint. Description adds valuable behavioral details: unknown/unlicensed ids are silently omitted, and compact:true returns slim summaries. No contradictions with 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 sentences, no wasted words. Key information front-loaded. Every sentence adds critical context: batching, pricing, omission behavior, compact option.

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, description mentions 'full records' vs 'slim summaries' but doesn't detail return format. Annotations cover safety/readonly. For a batch read tool, this is largely complete; could mention response structure but not critical.

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 good descriptions. Description adds meaning for 'compact' parameter ('slim summaries') and clarifies ids usage ('Pass an array of location ids'). Locale parameter not elaborated but schema covers it well. Overall adds value beyond schema.

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?

Clearly states 'Get details for MULTIPLE locations in one call (batch)', specifying verb, resource, and batching behavior. Distinguishes from sibling ta_get_location_details by noting it's a cheaper batch alternative.

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 when to use: 'cheaper than repeated ta_get_location_details'. Also covers edge cases: unknown/unlicensed ids silently omitted. Implicitly suggests using ta_get_location_details for single locations.

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