Estrutura organizacional

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

Annotations already cover the safety profile (readOnly, idempotent, non-destructive), so the description's added value is the provenance caveat: the open-data API does not publish the full tree, so this comes from the institutional portal. That is a genuinely useful disclosure about data trustworthiness and completeness. It stops short of mentioning pagination or how the limite cap interacts with totalSubordinadas, so it is not a 5.

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 purpose, the accepted input forms, and the return-shape breakdown are all front-loaded before the routing advice, and the source caveat closes it. It is dense with backticked field names but every clause carries information; only the return-shape enumeration is partly redundant with the output schema.

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 two-parameter read tool with annotations and an output schema, the description supplies everything the structured fields do not: the semantic meaning of caminho (superiors from the top down to the immediate superior) and of subordinadas (the entire subtree, including nuclei), plus the data-source caveat. Nothing needed to call it correctly is missing.

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%, so both parameters are already documented, and the description's note that unidade accepts a sigla or a full name only restates the schema. The limite parameter and its interaction with totalSubordinadas is never mentioned. Baseline 3 is correct when the schema does the heavy lifting.

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?

States a specific resource (the Senate's organizational chart down to service level) and the exact operation (given a unidade, return its superior path and full subordinate subtree). It explicitly names the sibling it is not — senado_servidores — and the different question that tool answers, so an agent can route without opening either schema.

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?

Gives concrete question shapes this tool answers ('o que está sob a DGER', 'quais secretarias/serviços pertencem a X') plus an explicit exclusion: to count or list servants under a unit, use senado_servidores with subordinadasA. When-to-use and when-to-use-something-else are both stated.

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