excluir_cliente

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

With no annotations, the description must cover behavioral traits. It only says 'Excluir', indicating a destructive action, but does not disclose whether deletion is permanent, if cascading effects occur, or if special permissions are required. This is a significant gap for a deletion tool.

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 with no redundant information. It front-loads the purpose and immediately provides the prerequisite, achieving high efficiency.

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 it is a simple destructive tool with one parameter and no output schema, the description covers the essential context: what it does and the prerequisite step. However, it lacks behavioral details such as irreversibility, which would be helpful for an agent. It is adequate but not fully complete.

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 coverage is 0% (no descriptions in the input schema). The description does not explicitly add meaning to the parameter 'id_cliente', but the prerequisite step ('Busque o ID do cliente') provides implicit context that this ID comes from a prior search. With a single, self-explanatory parameter, the lack of explicit detail is marginally acceptable.

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 function as 'Excluir um cliente/contato do Ploomes CRM', using a specific verb (Excluir) and resource (cliente/contato). It distinguishes from siblings like 'buscar_clientes' and 'salvar_cliente', which are search and save operations.

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 explicit prerequisites: 'Busque o ID do cliente a ser excluido usando buscar_clientes.' This guides the agent on when to use the tool (when the correct ID is obtained) and implies that it should not be used without a valid ID. However, it does not mention when not to use it (e.g., if deletion is irreversible) or alternatives.

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