excluir_webhook

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

No annotations are provided, so the description carries full burden. It states deletion but offers no further behavioral details such as required permissions, side effects, irreversibility, or error handling. This is minimal disclosure.

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 short: one sentence plus a prerequisite. It avoids unnecessary fluff but could be better structured with bullet points. Overall, it is concise and front-loaded.

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 tool with one parameter and no output schema, the description provides the core purpose and a prerequisite. However, it lacks details on what happens after deletion (return value, success/failure signals) and potential errors.

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 coverage is 0%, yet the description adds no information about the id_webhook parameter beyond the prerequisite. It fails to explain the purpose, format, or constraints of the parameter, which the agent needs to know.

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 deletes a webhook from Ploomes CRM. The verb 'Excluir' and resource 'webhook' are specific, and it distinguishes from other excluir_* sibling 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?

The description explicitly lists a prerequisite: obtaining the webhook ID using buscar_webhooks. This gives clear context for when and how to use this tool. However, it does not mention when not to use or discuss alternatives.

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