List Mail Webhooks

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

No annotations are provided, so the description carries the burden of behavioral disclosure. It indicates a read-only list operation, but does not disclose any additional behavior such as pagination, error handling, or what happens if the order id is invalid. While the listing nature is clear, no extra context is added.

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 a single concise sentence with no filler. It front-loads the action and scope, earning a high score for efficiency.

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 list operation with one parameter and no output schema, the description is sufficient for an agent to understand the basic function. However, it lacks any mention of return payload or behavior on missing order, so it's not fully complete, but the simplicity keeps it above average.

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?

The input schema has a single parameter 'order_id' with description 'Mail order ID', which is 100% coverage. The description repeats essentially the same information ('for a mail order') without adding further meaning about the parameter's format, constraints, or usage.

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 uses the verb 'List' and specifies the resource 'webhooks' scoped to 'a mail order,' clearly distinguishing it from sibling tools like mail_webhooks_get (which retrieves a single webhook) and mail_webhooks_create. It states exactly what the tool does.

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 usage is implied by the name and scope but there is no explicit guidance on when to use this tool versus mail_webhooks_get or other webhook operations. It does not mention alternatives or when-not-to-use scenarios, so it only partially meets the criteria.

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