sei_assinar_documentos_bloco

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

It discloses automatic authentication, mandatory cargo (failure if omitted), and fallback behavior (list options). Annotations (readOnlyHint false, destructiveHint false) are consistent, and the description adds useful behavioral context beyond them.

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, well-structured with a bullet list. Front-loaded with main purpose, each sentence adds value without redundancy. Ideal length for its complexity.

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 simple tool (2 parameters, no nested objects, output schema present), the description covers input behavior, usage quirks, and error recovery. It is fully complete for an agent to invoke correctly.

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 fully compensates by explaining each parameter: documentos (comma-separated IDs) and cargo (mandatory, lists options if omitted). This adds significant meaning beyond the schema's type and default.

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 it signs specific documents from a signature block ('Assina documentos específicos de um bloco de assinatura'). This distinguishes it from related tools like 'sei_assinar_documento' (single document) and 'sei_assinar_bloco' (whole block).

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?

It explains when to use: requires cargo parameter, and if unknown, call without cargo to list options. It instructs to ask the user and save the cargo for reuse. This provides explicit guidance on handling a missing parameter.

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