sei_pesquisar_blocos_assinatura

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

Annotations already signal read-only and open-world behavior. The description adds no behavioral context such as pagination limits, result ordering, or side effects. It does not clarify what 'pesquisar' entails beyond a basic search.

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 sentence, which is concise but fails to include necessary details. It is not well-structured; it only states purpose without layering information.

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 2 parameters with no schema descriptions and an output schema (unknown), the description is insufficient. It does not cover return format, filtering logic, or limit behavior, making it incomplete for effective use.

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 0%, so the description must explain parameters. It does not. 'limit' and 'filtro' are left to inference, with no details on format, allowed values, or behavior.

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 searches for existing signature blocks ('Pesquisa blocos de assinatura existentes'), with a specific verb and resource. It distinguishes from sibling tools that create, modify, or list specific aspects of signature blocks.

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?

No guidance on when to use this tool versus alternatives like sei_listar_blocos_documento or sei_listar_documentos_bloco_assinatura. There is no mention of use cases, prerequisites, or context.

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