excluir_numero_funcionarios

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

With no annotations, the description carries full burden. It states the tool deletes an option, implying destructive behavior, but does not disclose consequences such as whether deletion is permanent, cascading effects, or authorization requirements. This is minimal disclosure for a mutation operation.

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 a single sentence of 7 words, achieving conciseness. However, it may be too minimal, lacking any context beyond the basic action. It is structured well for quick reading.

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's simplicity (1 param, no output schema), the description should at least explain the parameter's meaning and return behavior. It fails to do so, making it incomplete for an agent to use correctly without external knowledge.

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 schema has one parameter 'id_opcao' with 0% description coverage. The description adds no information about this parameter, leaving the agent to guess what kind of ID is needed or how to obtain it.

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 'Excluir uma opcao de numero de funcionarios do Ploomes CRM' clearly states the verb (excluir), resource (opcao de numero de funcionarios), and system (Ploomes CRM). It differentiates from sibling delete tools like excluir_cliente or excluir_peca_produto by specifying the resource type, but could be more precise about what exactly an 'option of number of employees' is.

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 like salvar_numero_funcionarios or buscar_numero_funcionarios. There is no mention of when not to use it or any prerequisites.

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