sei_excluir_grupo_acompanhamento

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

The description confirms deletion ('exclui'), which aligns with the destructiveHint=true annotation. However, it adds no additional behavioral context beyond what annotations already provide, such as side effects or required permissions.

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 extremely concise with two short sentences: one for the action and one for the input format. No redundant information, every word earns its place.

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 delete action and annotations, the description covers the basic purpose and input format. However, it omits details like whether the deletion is permanent, what happens to associated data, or any confirmation requirements. An improved description could add more context for completeness.

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 for the single parameter, the description adds crucial format information: IDs are comma-separated. This compensates for the schema gap and clarifies usage.

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 action ('Exclui grupo(s) de acompanhamento especial') and distinguishes it from sibling tools like creating or listing groups. The verb 'Excluir' and the resource are specific.

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 mentions using comma-separated IDs but provides no explicit guidance on when to use this tool versus alternatives. The context implies deletion, but lacks when-not or prerequisites.

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