consultar_categoria

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

With no annotations provided, the description carries the full burden of behavioral disclosure. It indicates a read-only query operation and adds context about the included 'dadosDRE' field, but it does not describe the return type, error behavior, or required permissions, leaving some ambiguity for an agent.

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, front-loaded sentence with no filler or repetition. Every part adds value: the action, the resource, the identifying parameter, and the specific linked data included.

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?

The tool is simple (one parameter, no output schema), so the description covers the core purpose and a key part of the response ('dadosDRE'). However, with no output schema, the description is incomplete regarding the full set of returned details and does not address not-found or error scenarios, which a fully transparent description would include.

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 only defines 'codigo' as a required string; the description adds meaning by stating the category is identified 'pelo código' (by code), clarifying how the parameter is used. While it does not detail format or constraints, for a single parameter this is a meaningful enhancement over the raw schema.

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 uses a specific verb ('Consulta') and resource ('categoria pelo código'), clearly stating the tool's function: query details of a single category by its code. It also mentions the inclusion of linked DRE account data, which distinguishes it from sibling tools like listar_categorias (listing all categories) or incluir_categoria/alterar_categoria (mutations).

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 the tool is for retrieving one category's details by code, providing clear context for its primary use. However, it does not explicitly mention alternatives or cases where another tool (e.g., listar_categorias) would be more appropriate, nor does it state when not to use it.

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