get_city_stats

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

No annotations are supplied, so the description carries the full burden. It does add real behavioral value by disclosing the cost profile ('[FREE]') and enumerating the returned metrics, which matters since there is no output schema. It says nothing about data freshness, units (what currency GDP/wealth are in), or result size for the all-cities case.

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?

Front-loaded with the free-tier marker and the metric list, then the valid values, then the multiplier reference, then the default behavior. Dense and largely waste-free; the multiplier line is reference data rather than prose bloat. Minor redundancy between the city list and 'all 10 cities'.

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?

For a one-optional-parameter read tool with no annotations and no output schema, the description covers what it returns, what values are legal, and what the empty default does. The remaining gaps — units, freshness, and differentiation from get_city_pulse — are real but secondary.

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 0% — the lone 'city' parameter has no description and no enum, so the description must compensate. It largely does: it lists all ten valid city strings, states the empty-string default returns all cities, and even gives per-city pay multipliers. That is strong compensation, but the parameter still lacks any stated matching convention (case sensitivity, exact vs partial names), keeping it below a 4.

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?

States a specific verb+resource ('Get stats for AgentWorld cities') and enumerates exactly which metrics are returned: agent count, avg wealth, GDP, pay multiplier. Very clear on its own. It does not, however, distinguish itself from plausible siblings such as get_city_pulse or get_economy, so an agent cannot tell from the description alone which of those to pick.

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?

Gives one concrete usage rule — 'Leave city empty to get all 10 cities' — which is genuine when-to-use guidance for the optional parameter. It offers no guidance on when to prefer this over sibling city/economy tools, and no exclusions.

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