sei_criar_grupo_acompanhamento

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

Annotations already indicate readOnlyHint=false (write operation) and destructiveHint=false. The description adds 'Cria' (creates) but does not clarify side effects (openWorldHint=true) or what 'especial' implies. No behavioral details beyond what annotations already convey.

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 short (one sentence) but wastes no words. However, the brevity sacrifices necessary context. It could be expanded without becoming verbose.

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?

There is an output schema (not shown) but the description does not mention what the tool returns (e.g., created group ID). For a simple creation tool, the description should cover basic inputs and outputs. It is incomplete.

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?

The single parameter 'nome' has no description in the schema (0% coverage) and the description does not explain its purpose, format, or constraints. The agent is left to guess that 'nome' is the group name.

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 states it creates a special monitoring group ('grupo de acompanhamento especial') in SEI. The verb 'Cria' and resource are specific, and it distinguishes from sibling tools like 'sei_excluir_grupo_acompanhamento' (delete group) and 'sei_acompanhar_processo' (add process to monitoring), but doesn't explain what 'especial' means.

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 guidance on when to use this tool vs alternatives such as 'sei_acompanhar_processo' for process-level monitoring or 'sei_criar_bloco_interno' for internal blocks. The description provides no context for decision-making.

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