sei_incluir_documento_bloco_assinatura

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

Annotations indicate readOnlyHint=false and destructiveHint=false, so the description's verb 'inclui' (include) is consistent. However, the description adds no further behavioral context beyond what annotations provide, such as side effects or state changes.

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 extremely concise with two short sentences for the tool purpose and a bulleted parameter list. No unnecessary words, perfectly front-loaded.

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 simple write tool with two required parameters and an output schema, the description covers purpose and parameter semantics adequately. It could mention the prerequisite that the signature block must exist, but overall it is sufficient.

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?

With 0% schema description coverage, the description adds valuable detail: it explains the id_bloco parameter as 'ID do bloco de assinatura' and documentos as 'ID(s) de documento(s) separados por vírgula', clarifying the input format for the comma-separated list.

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 action 'Inclui documento(s) em um bloco de assinatura' (include documents in a signature block) and the target resource. It distinguishes from sibling tools like sei_retirar_documentos_bloco_assinatura (remove) and sei_listar_documentos_bloco_assinatura (list).

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 explicit guidance on when to use this tool versus alternatives. The description implies it is for adding documents to an existing block, but does not mention prerequisites, when not to use, or relationships with other tools like sei_criar_bloco_assinatura.

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