sei_incluir_processo_bloco_interno

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

Annotations indicate readOnlyHint=false (mutating) and destructiveHint=false, but the description adds no behavioral details such as side effects, permission requirements, or limits. It only explains parameter format.

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 very concise with two lines of purpose and two lines of parameter info. It is front-loaded and to the point, though the parameter info could be integrated more elegantly.

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 is simple (2 required params) and has an output schema, the description covers the basics but lacks context about success/error behavior, block existence requirements, or output meaning. It is minimally adequate.

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?

Despite 0% schema description coverage, the description adds meaningful parameter explanations: id_bloco is explicitly 'ID do bloco' and processos is 'IdProcedimento(s) separados por vírgula', which clarifies the comma-separated format beyond the schema 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 'Inclui processo(s) em um bloco interno' (includes process(es) in an internal block), using a specific verb and resource. It distinguishes from sibling tools like sei_retirar_processo_bloco_interno (remove) and sei_criar_bloco_interno (create 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?

The description provides no guidance on when to use this tool versus alternatives. It does not mention prerequisites (e.g., block must exist) or context. Sibling tools like sei_criar_bloco_interno are not referenced.

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