get_city_sanitation

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 discloses the data source (2022 Census) and the subject (sanitary sewage coverage), but does not mention any behavioral traits such as data freshness, limitations, or whether the data is static. For a simple parameterless tool, this is adequate but not thorough.

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 is clear and to the point. It contains no fluff and is efficiently 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 (no parameters, no output schema), the description provides adequate context. However, it does not describe the return format or structure, which slightly reduces completeness for an agent expecting structured data.

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 tool has zero parameters, and the schema coverage is 100% (trivially). According to the guidelines, the baseline is 4 for 0 parameters. The description does not need to add parameter information.

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 'obtém' (obtains) and the specific resource: 'panorama geral de cobertura do esgotamento sanitário de Natal (Censo 2022)'. This distinguishes it from the sibling tool get_neighborhood_sanitation, which likely provides per-neighborhood data.

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 city-level overview but does not explicitly state when to use this tool over the sibling get_neighborhood_sanitation. No exclusions or alternatives are mentioned, but context is somewhat clear.

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