city_context

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

No annotations are provided, so the description carries full burden for behavioral disclosure. It only states what the tool returns but does not mention whether it is read-only, requires authentication, or has any side effects. For a data retrieval tool, such transparency is expected.

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 a single sentence that directly communicates the tool's purpose without extraneous details. Every word is essential, making it highly concise and front-loaded.

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?

The description adequately explains the tool's result (city with country and region) but does not elaborate on potential complexities, such as whether the city ID must exist or how missing country/region data is handled. Given the simple parameter set and no output schema, it is minimally complete but could add more context about the combined response.

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 parameter descriptions clearly stating 'City UUID' for id and 'Comma-separated BCP 47 language tags' for preferredLanguages. The description adds no additional meaning beyond what the schema already provides, so a baseline score of 3 is appropriate.

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 gets a city along with its full country and region details, using the specific verb 'Get' and resource 'city'. This distinguishes it from siblings like 'get_city' (which likely returns only city data) and 'country_overview' (which returns country data without city).

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 implies usage when a combined view of city, country, and region is needed, but it does not explicitly state when to use this tool instead of calling individual tools like 'get_city', 'get_country', and 'get_region' separately. No alternatives or exclusions are mentioned.

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