excluir_checklist_etapa

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

No annotations are provided, so the description must convey behavioral traits. It only states 'Excluir' (delete), which implies destruction but does not warn about irreversibility, permission requirements, or side effects. For a deletion tool, this is insufficient transparency.

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 two sentences with no wasted words. The purpose is front-loaded, followed by a prerequisite. Every sentence is necessary and concise.

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?

The tool has only one required parameter and no output schema, but the description is minimal. It lacks details about error handling, return values, or behavioral traits like irreversibility. Given the simplicity of the operation, the description is still incomplete for a safe deletion.

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%, but the description adds no meaning to the 'id' parameter beyond the schema's type 'integer'. It does not explain that the ID represents the checklist identifier or how to obtain it, though the prerequisite hints at it. The description fails to compensate for the lack of schema explanations.

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 action ('Excluir', to delete), the resource ('checklist de etapa de pipeline'), and the system ('Ploomes CRM'). It distinguishes from sibling tools like 'salvar_checklist_etapa' and 'buscar_checklists_etapa' by specifying deletion.

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 prerequisite guidance: 'Use buscar_checklists_etapa para obter o ID do checklist a ser excluido.' This tells the agent when to use this tool (after fetching the ID) and gives a clear context. No exclusions or alternatives are mentioned, which is acceptable for a simple delete operation.

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