excluir_secao_campo

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

Description indicates a destructive action (delete) but does not elaborate on side effects, reversibility, or required permissions. With no annotations, the description carries full burden, yet it remains minimal.

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?

Description is very short (one sentence), making it concise but lacking structure or front-loading of key info. It is not verbose, but it is also not particularly well-organized.

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?

For a simple delete operation with one parameter and no output schema, the description is minimally adequate but does not explain return behavior, prerequisites, or post-conditions. Could be more 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?

The single parameter 'id_secao' has no description in the schema, and the tool description does not explain what the ID refers to, how to obtain it, or any constraints. Schema coverage is 0%, so the description should compensate but fails to.

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?

Description clearly states the action 'Excluir' (delete) and the resource 'secao de campos personalizados do Ploomes CRM' (section of custom fields). It distinguishes from sibling tools like 'excluir_secao_formulario_pipeline' which targets pipeline form sections.

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 provided on when to use this tool versus alternatives like 'salvar_secao_campo' or 'excluir_campo'. Lacks explicit when/when-not or context for selection.

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