excluir_pipeline

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

No annotations are provided, so the description must fully disclose behavioral traits. It states the delete action but does not mention that it is destructive, irreversible, or any specific authorization needs. For a delete tool, this lack of transparency is a significant gap.

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 concise, consisting of two short sentences. It front-loads the main action and then lists prerequisites. No unnecessary information is present, though a bit more structure could help readability.

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 (one parameter, no output schema), the description covers the basic purpose and a prerequisite. However, it lacks important behavioral context such as irreversibility and potential effects, which are critical for a delete operation.

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%, so the description must compensate. It mentions that the ID comes from 'buscar_pipeline', which adds some context beyond the schema, but it does not explain the format or constraints of the 'id_pipeline' parameter. The added value is minimal.

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's purpose: 'Excluir um pipeline/funil de negocios do Ploomes CRM.' It uses a specific verb ('Excluir') and resource ('pipeline/funil'), distinguishing it from sibling tools like 'salvar_pipeline' or 'buscar_pipeline'.

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 clear prerequisite: 'Busque o ID do pipeline a ser excluido usando buscar_pipeline.' This tells the agent when to use the tool (after obtaining the ID). It implicitly sets a usage condition but does not explicitly mention when not to use it or alternatives.

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