List webhooks

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

With no annotations, the description bears full responsibility for disclosing behavior. It mentions cursor pagination and 400 error handling, which are useful, but does not explicitly state idempotency or read-only nature (implied by GET but not stated). Lacks information about rate limits or authorization 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 highly concise: three sentences that efficiently convey the tool's purpose, pagination support, and error behavior. The key information is front-loaded, and every sentence contributes meaningful content.

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 4 parameters (one being a free-form query object) and no output schema, the description covers pagination and error handling but lacks response structure details and warnings about the query parameter's loose typing. Adequate but not fully comprehensive.

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 100%, so parameters are already documented. The description adds minimal value: it mentions 'cursor pagination' (aligns with cursor parameter) and 'field names follow the Loyverse API', but does not elaborate on parameter usage or constraints beyond what the schema provides. Baseline of 3 is appropriate.

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 'List webhooks from Loyverse' and includes the HTTP method and endpoint (GET /webhooks), making the tool's purpose unmistakable. It is easily distinguishable from sibling list tools due to the specific resource (webhooks).

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 no guidance on when to use this tool versus alternatives, nor does it mention prerequisites or context-specific constraints. It only describes the tool's own functionality without any comparative or exclusionary advice.

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