tickerbot_list_webhooks

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

With no annotations provided, the description carries the burden of behavioral disclosure. It adds useful context (caller's scope, newest-first ordering) but does not explicitly state that the operation is read-only or describe return format/pagination behavior. The verb 'List' implies safety, but explicit confirmation is absent.

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?

Two sentences, front-loaded with the core purpose and a targeted usage tip. Every word earns its place; no fluff or redundancy.

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 tool with no output schema, the description covers scope, ordering, and filtering. It does not explain the response structure or pagination beyond what the schema provides, but the essential information for invoking the tool correctly is present. Slight gap in return value details, though acceptable given the tool's simplicity.

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 100%, so all parameters are already documented. The description adds a mention of filtering by 'status' but provides no additional syntax or semantics beyond the schema. It reinforces existing information without expanding on parameter meaning.

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 action ('List'), the resource ('the caller's webhook subscriptions'), and a differentiator ('newest-first'). It also distinguishes from siblings like 'tickerbot_list_webhook_deliveries' and 'tickerbot_get_webhook' by focusing on subscriptions overview.

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 gives clear context for when to use the tool and specifically instructs how to use the 'status' parameter to filter. However, it does not explicitly mention when to prefer this over related tools (e.g., get_webhook for a single subscription or list_webhook_deliveries for delivery logs).

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