get_neighborhood_income

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

No annotations are provided, so the description bears full weight. It discloses the data source (Censo 2022) and clarifies the income unit (household head), but does not mention whether the operation is read-only, any authentication needs, rate limits, or error behavior. Incomplete for a tool with zero annotation coverage.

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 consists of two concise sentences: the first explains what the tool does, the second adds a critical usage nuance. No redundancy, 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?

Given the tool has one required parameter, no output schema, and no annotations, the description is largely sufficient: it specifies the metric, geographic scope, and data source. Missing are details on output format (e.g., returns a number or object) and error handling, but for a simple retrieval tool this is minor.

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 100% for the single parameter 'query', which is clearly described as 'Nome do bairro ou código de 10 dígitos.' The tool description adds no further meaning beyond what the schema provides, so baseline 3 applies.

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 specifies the tool gets average and median nominal monthly income of household heads in a specific neighborhood of Natal from Censo 2022. It distinguishes from siblings like get_average_income (general) and get_neighborhood_demographics (broader).

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 includes a caution about the metric being for household heads, not municipal income, but does not explicitly state when to use this tool versus alternatives like get_average_income or compare_neighborhoods. Usage context is implied (neighborhood-specific income in Natal).

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