Get area-specific contextual information.
Args: area: "southwark", "london", or a specific neighbourhood.
Returns local context document (markdown).
| Name | Required | Description | Default |
|---|---|---|---|
| area | No | southwark |
| Name | Required | Description | Default |
|---|---|---|---|
| result | Yes |
Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
No annotations are provided, so the description carries the burden. It discloses the return format (markdown) and allowed area values ('southwark', 'london'), but doesn't mention error behavior, read-only status, or handling of unrecognized areas. This adds some context but leaves gaps.
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 extremely concise: one purpose sentence, an Args line, and a Returns line. It front-loads the main intent, avoids redundancy, and every sentence adds value.
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 tool is simple with one parameter and has an output schema, so the description is minimally sufficient. However, it lacks differentiation from sibling KB tools and does not clarify what 'contextual information' encompasses, which is a gap for a knowledge base tool.
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 0%, so the description provides the only semantic meaning for the 'area' parameter. It gives concrete examples ('southwark', 'london') and mentions that any specific neighbourhood is allowed, significantly extending the schema's bare default.
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 area-specific contextual information, with a specific verb ('Get') and resource. It distinguishes from sibling KB tools by focusing on 'local context' and returning a markdown document, though the nature of 'contextual information' could be more explicit.
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?
There is no guidance on when to choose this tool over siblings like kb_get_guidelines or kb_get_health_effects. The description only implies usage for area-specific context without explicit exclusions, alternatives, or prerequisites.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.
Add one secure layer between your agents and this server.
Three tools (assess_location_aq, get_current_aq, get_aqi_summary) all provide current air quality and health context, creating potential misselection. The assess tool is positioned as the default entry point, but the boundaries between detailed readings, AQI summary, and comprehensive assessment could confuse an agent. Other tools are more clearly distinct.
Most tools follow a verb_noun pattern (get_current_aq, list_monitors, chart_aq_trend), but three use noun phrases (regulatory_stats, time_patterns, trend_analysis). The kb_ prefix is used consistently for knowledge base lookups. Overall conventions are mostly consistent with minor deviations.
15 tools is at the upper end of the ideal range and each serves a distinct function within the air quality domain, from current conditions to historical trends, comparisons, and regulatory compliance. No tool feels redundant, and the count is appropriate for the server's stated purpose.
The tool set covers current conditions, historical data, trend analysis, temporal patterns, location comparisons, regulatory statistics, monitor discovery, and a knowledge base for guidelines, health effects, and practical advice. This is a comprehensive surface with no glaring missing operations for the domain.