excluir_campo_formulario_proposta

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

No annotations are provided, so the description carries the full burden. It discloses that the tool removes a field (destructive), but does not explicitly state if the action is irreversible, requires specific permissions, or affects related data. It adds context about the field being from a form section and the tool being new, but lacks deeper behavioral details.

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 well-structured with clear sections, front-loaded purpose, and only necessary details. It could be slightly more concise, but every sentence adds value, including prerequisites and exclusions.

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 (single parameter, no output schema), the description covers purpose, usage, and alternatives. It does not mention side effects on collections or return values, but the core decision-making context is sufficient.

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, the description must compensate. It implies the 'id' parameter is the field ID obtained via buscar_formulario_proposta, but does not explicitly name it or describe its format beyond integer. This provides some context but leaves the parameter's semantics partially implicit.

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 'Remover um campo de uma seção do formulário de um modelo de Proposta/Venda/Documento', specifying the verb and resource. It distinguishes itself from the sibling tool excluir_campo_formulario_pipeline by noting it's for the Proposta/CPQ side, and from block removal tools by explicitly excluding product/parcel blocks.

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 a prerequisite (use buscar_formulario_proposta to get the field ID), explicitly states when NOT to use it (for removing a block of products/parcelas), and gives an alternative tool (salvar_modelo_proposta). It also mentions the equivalent pipeline tool, offering comprehensive guidance.

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