excluir_equipe

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

No annotations are provided, so the description must disclose behavioral traits. It only states 'Excluir' (delete), implying destruction, but does not mention permanence, side effects, permissions required, or cascading deletions. For a deletion tool, this lack of detail is a significant gap.

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: two sentences stating purpose and prerequisite. It is front-loaded with the key action and avoids any unnecessary words.

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 no annotations or output schema, the description should cover behavioral aspects and parameter details. It only covers purpose and a prerequisite, leaving out critical information like side effects, reversibility, and parameter semantics, which is insufficient for a deletion tool.

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?

Schema description coverage is 0%. The description does not explain the 'id_equipe' parameter beyond referencing how to obtain it. It does not specify format, constraints, or additional context, leaving the agent with minimal guidance for constructing valid input.

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 tool's purpose: 'Excluir uma equipe do Ploomes CRM', specifying the verb (excluir/delete) and resource (equipe/team). It is distinct from sibling tools like 'excluir_cliente' or 'excluir_produto'.

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 includes a prerequisite: 'Busque o ID da equipe a ser excluida usando buscar_equipes_de_usuarios', guiding the agent to first retrieve the team ID. However, it does not provide guidance on when not to use this tool or alternatives for different deletion scenarios.

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