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

The description adds context beyond annotations: it mentions prepaid credit (payment requirement) and that no platform credentials are needed, which are useful operational details. However, it does not disclose other behavioral aspects like rate limits, error handling, or data refresh cadence. It aligns with readOnlyHint and idempotentHint, so no contradiction, but the added value is moderate.

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 paragraph of four sentences, but includes redundancy (e.g., 'consulta em fonte oficial' and 'Consulta informação de fontes e órgãos oficiais' repeat the official-source theme) and legal boilerplate (LGPD) that could be trimmed. It is not overly long, but not tightly structured; the essential information could be conveyed in fewer sentences.

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?

For a tool with two parameters and no output schema, the description lacks parameter documentation and return-value expectations. It provides background on official data and payment, but does not explain how to input the property registration number or what the query result looks like. This leaves the agent under-informed for correct invocation and result interpretation.

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 description coverage is 0%, so the description must compensate by explaining parameters, but it does not. Neither 'inscricao_imovel' nor 'exercicio' are described. The only hint is 'consulta' implying a lookup, but no parameter meaning, format, or constraints are provided. This is a significant gap.

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 queries IPTU data from official SEFAZ DF sources, using the verb 'consulta' and specifying the resource. It distinguishes from generic platform siblings like authenticate or report_bug, which are unrelated. The phrase 'Emissão Guia' adds a potential action, but the primary purpose is a query, so it's clear enough though slightly ambiguous.

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 provides no explicit guidance on when to use this tool versus alternatives, nor does it mention exclusions or conditions. It implies usage for IPTU queries but lacks any 'when to use' or 'when not to use' statements. The siblings are unrelated, so differentiation is not critical, but the absence of any usage context leaves the agent without decision support.

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