list_user_webhooks

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

No annotations are provided, so the description must carry the full behavioral burden. 'List' implies a read-only operation, but the description says nothing about pagination, continuation tokens, authentication scope, or rate limits. It mostly restates the tool's core function without disclosing additional behavior.

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?

A single, tightly worded sentence that front-loads the resource and scope. Every word earns its place; there is no filler or redundant phrasing.

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 one-parameter tool with an output schema, the description is mostly adequate. However, the lack of any guidance around pagination/continuation and the absence of any notes distinguishing this from sibling tools leave a noticeable gap, though the low complexity softens the impact.

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% for the single 'continuation' parameter, and the description does not mention or explain it. The schema's name and default null hint at pagination, but the description adds no semantic value to help the agent use the parameter correctly.

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 a specific verb ('List') with a clear resource ('webhooks') and a precise scope ('current user account'). This scope distinguishes it from the sibling 'list_organization_webhooks' without needing to inspect schemas.

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 phrase 'current user account' clearly signals when to use this tool versus organization-level webhook tools such as list_organization_webhooks. It does not explicitly name alternatives or state when not to use it, but the context is clear for a simple listing tool.

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