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

Annotations already declare readOnlyHint, idempotentHint, and destructiveHint, establishing a safe read operation. The description adds useful behavioral context: the exact HTTP endpoint and an explicit pagination mechanism (pagina/quantidade_registros), going beyond the annotations.

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, information-dense sentence with no redundant content. It front-loads the core purpose and then explains key parameters in a straightforward manner.

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's main complexity lies in the filtro object, which is left undefined ('conforme a API'), creating ambiguity for agents. There is no output schema, and the description does not describe return values. Pagination is covered, but the filter structure and expected response are significant gaps, making it adequate but not complete.

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 has 0% description coverage, so the description must compensate. It clarifies that filtro specifies criteria according to the API and that pagina/quantidade_registros are for pagination. This gives meaning to all three parameters, though the inner structure of filtro remains opaque.

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's purpose: 'Busca Intimações/publicações por filtro' (search notices/publications by filter) and provides the endpoint POST /intimacao/consulta. It is distinct from siblings like projuris_get_intimacao, which likely fetches a single record by ID.

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 a filtered search use case via 'por filtro' and mentions pagination, but it does not explicitly state when to use this tool versus alternatives such as projuris_get_intimacao or other consulta tools. No exclusions or alternative tool names are given.

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