buscar_webhooks

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

The description discloses pagination behavior ('resultado da busca eh limitado a resultados por pagina'), which is important. However, with no annotations, it fails to mention that this is a read-only operation, default page size, or any authentication requirements.

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 very short with no extraneous text, but it lacks necessary details. It is concise but under-specified, earning a neutral score.

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 tool with 0% schema coverage, no output schema, and no annotations, the description is insufficient. It does not explain return values, filtering options beyond pagination, or error conditions. An agent would struggle to invoke this tool correctly without additional context.

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 does not explain the purpose of parameters 'id', 'nome', or 'pagina'. It only indirectly hints at pagination via the note. The agent has no information on how to use these parameters for filtering.

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 searches for webhooks in Ploomes CRM, but it does not differentiate from the sibling tool 'buscar_acoes_webhook' which might refer to actions of a webhook. The plural 'webhooks' implies listing all, but explicit distinction is missing.

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?

No guidance on when to use this tool versus alternatives like 'buscar_acoes_webhook' or 'buscar_webhook' (singular). No prerequisite conditions or exclusion criteria are mentioned.

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