numbeo_indices_city

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

No annotations provided; description notes 'Credential-free public Numbeo data' implying read-only and no auth, but does not disclose error handling, rate limits, or caching behavior. Adequate for a simple data retrieval tool.

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 clear sentences with no extraneous content. Front-loaded with primary purpose.

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 and simple parameters, the description explains inputs and outputs adequately but lacks error/edge case info. Could mention response format or example usage.

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 description coverage is 100% with minimal param descriptions. Tool description adds context by explicitly listing index families and result structure, but does not further detail slug format or valid values 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 it retrieves a Numbeo city's data for an index family. Lists valid families and describes result structure, distinguishing it from sibling tools like numbeo_cost_of_living_city or numbeo_indices_country.

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?

No explicit guidance on when to use this tool over siblings. The description implies city-level index data, but does not address selection criteria or prerequisites.

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