sei_anotar_documento_bloco_assinatura

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

Annotations already indicate non-read-only (readOnlyHint=false) and non-destructive (destructiveHint=false). The description adds version availability and a troubleshooting hint for unexpected errors, but does not disclose details like whether the annotation can be modified, deleted, or its impact on the document.

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 concise with two sentences: the first states the purpose, the second provides version and error guidance. No redundant information, and the key action is 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?

Given the tool has an output schema (unseen), the description does not need to detail return values. However, it lacks parameter descriptions and usage conditions, which would improve completeness. It is minimally adequate but not comprehensive.

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 coverage is 0% (no parameter descriptions). The description does not explicitly define id_bloco, documento, or descricao beyond what is implied by the tool's name and purpose. Users must infer meanings, which is insufficient for a tool with three required parameters.

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: 'Cria anotação em documento dentro de um bloco de assinatura.' This is a specific verb (cria) and resource (annotation on document in signature block), and it distinguishes from sibling tools like sei_criar_anotacao and sei_anotar_processo_bloco_interno.

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 usage for annotating a document inside a signature block but offers no explicit guidance on when to use this tool versus alternatives like sei_criar_anotacao for process-level annotations. There is no mention of when-not-to-use or workflow context.

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