excluir_modelo_proposta

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

Explicitly states 'soft delete' and warns about side effects of deleting default or used templates. With no annotations provided, the description fully carries the burden of behavioral disclosure and does so thoroughly.

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 somewhat verbose, including a historical note (NOVO) and a caution. While structured, it could be more concise without losing essential information.

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?

Covers purpose, prerequisites, and warnings. As a simple delete operation with one parameter and no output schema, the description is largely complete. However, it could mention success/error responses or irreversibility (though 'soft delete' implies reversibility).

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 indirectly explains the 'id' parameter by mentioning 'obter o Id (DocumentTemplateId)' in the prerequisite, but does not formally describe the parameter's meaning or constraints. It adds some value but could be more explicit.

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 does 'Excluir (soft delete) um modelo de Proposta/Venda/Documento (PVD) do Ploomes CRM.' It specifies the verb (excluir/soft delete) and the resource (modelo de PVD), distinguishing it from other excluir tools for different entities.

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?

Provides prerequisites (use buscar_templates_documentos to get the Id) and a caution about deleting default or used templates. This gives clear context and guidance for intended usage, though it does not explicitly mention alternatives or when not to use.

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