sei_criar_bloco_assinatura

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

Annotations indicate it is not read-only and not destructive, but the description adds no behavioral context beyond the action of creation. It doesn't mention side effects, permissions, reversibility, or any state changes that may occur, which would be helpful 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 concise—one sentence for purpose followed by a bulleted list of parameters. No extraneous information, and the structure makes it easy to scan.

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 description adequately covers the creation function but does not mention output schema (which exists) or typical usage context (e.g., blocks are used to group documents for signature). It is minimal but sufficient for a simple tool with two parameters.

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 coverage, the description compensates by explaining each parameter: 'descricao' is the block description, 'unidades' accepts acronyms or IDs separated by commas and auto-resolves. This adds meaningful guidance beyond the schema's property titles.

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 'Cria um bloco de assinatura no SEI' (creates a signature block), which is a specific verb+resource. It distinguishes itself from sibling tools by the resource type (bloco_assinatura), but does not explicitly differentiate from other creation tools like sei_criar_documento or sei_criar_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 provides no guidance on when to use this tool versus alternatives. Siblings include creation tools like sei_criar_bloco_interno, but no context or prerequisites are given for using this tool.

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