get_city_profile

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

No annotations are provided, so the description carries the full burden. It mentions the tool returns a 'comprehensive profile' with 'air quality, funding, and metadata', but doesn't disclose behavioral traits like whether it's a read-only operation, if it requires specific permissions, rate limits, or error handling. The description is minimal and lacks crucial operational context.

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 appropriately sized and front-loaded, starting with the core purpose. The 'Args' and 'Returns' sections add structure without redundancy. However, the phrase 'including all available data' is slightly vague and could be more precise, but overall it's efficient with minimal waste.

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 the tool has an output schema, the description doesn't need to explain return values in detail, and it mentions key components like 'air quality, funding, and metadata'. However, with no annotations and a simple input schema, the description lacks context on usage scenarios, error cases, or integration with sibling tools, making it adequate but with clear gaps.

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?

The description adds significant meaning beyond the input schema, which has 0% coverage. It specifies the 'city' parameter as 'City name (Delhi, Bangalore, Mumbai, etc.)', providing examples and clarifying it's a string input. This compensates well for the schema's lack of description, though it doesn't detail format constraints like case sensitivity.

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 verb ('Get') and resource ('comprehensive profile for a city'), specifying it includes 'all available data'. It distinguishes from siblings like 'compare_cities' or 'analyze_funding' by focusing on a single city's full profile. However, it doesn't explicitly contrast with 'query_table' or 'describe_table', which might overlap in data access.

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 guidance is provided on when to use this tool versus alternatives. For example, it doesn't mention if this is preferred over 'query_table' for city-specific data or when 'compare_cities' might be better for multi-city analysis. The description implies usage for a single city but lacks explicit exclusions or prerequisites.

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