get_neighborhood_sanitation

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

No annotations are provided, so the description must fully disclose behavioral traits. It only states the output (sanitation types and adequacy percentage) but does not mention read-only nature, authorization requirements, error handling for invalid neighborhoods, or rate limits. The description adds minimal behavioral context beyond the obvious retrieval operation.

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 immediately states the verb and output, with no redundant words or unnecessary details. It is perfectly 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?

Given the tool's simplicity (single required parameter, no output schema, no annotations), the description adequately specifies the input and output. It could explicitly note that results are scoped to Natal, but the phrase 'bairro específico de Natal' already implies this. Slight lack of detail about return format or edge cases prevents a perfect score.

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 schema has 100% description coverage, with the parameter 'query' described as 'Nome do bairro ou código de 10 dígitos.' The description adds no additional meaning beyond this, essentially rephrasing the same information. Baseline 3 applies since no extra value is provided.

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 retrieves complete sanitation details (types and adequacy percentage) for a specific neighborhood in Natal. It uses a specific verb ('Obtém') and resource ('detalhamento completo dos tipos de esgotamento sanitário'), distinguishing it from sibling tools like get_city_sanitation (city-level) and get_neighborhood_demographics.

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 for neighborhood-level sanitation data but provides no explicit guidance on when to use this tool vs alternatives (e.g., get_city_sanitation for city-wide data, or get_neighborhood_demographics for demographic data). No when-not-to-use or alternative tool mentions.

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