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

With no annotations, the description carries full burden, but only mentions 'Requires auth.' It does not disclose what the webhook registration does, whether it validates the URL, how the subscription is managed, or what happens on duplicates/updates. This is a significant transparency gap for a state-changing subscription tool.

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 short sentences with no filler. The primary action is front-loaded and the auth requirement is a discrete, useful addendum. Every word earns its place.

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?

The tool has three parameters, including an undocumented nested 'filters' object, no output schema, and no annotations. A two-sentence description is insufficient to convey webhook registration behavior, filter semantics, or expected response, making it incomplete for reliable invocation.

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%, so the description must clarify parameters. 'via webhook' hints at 'url' and 'real-time events' hints at 'events', but the 'filters' object is entirely unexplained, leaving a required structural element opaque.

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 ('Subscribe') and resource ('real-time events via webhook'), clearly distinguishing this tool from siblings like get_listing or list_bounties. The purpose is unambiguous and immediately understandable.

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 clear context (use for real-time event subscriptions) and an explicit prerequisite (requires auth), but does not mention alternatives or exclusions. It is more than implied, yet lacks explicit when-not guidance.

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