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

Annotations indicate idempotentHint=true, but the description says 'Returns the new subscription id,' implying each call creates a new subscription, which could contradict idempotency. However, the description does not explicitly address idempotency or deduplication. It adds extensive behavioral details: authentication requirement, type-specific parameters, delivery channel nuances (SMS cap, webhook auto-disable, signing). The contradiction is mild, but the description could be more transparent about the idempotency model.

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 fairly long but well-structured: purpose first, then requirements, supported types, delivery options. Every sentence adds value—no fluff. It could be slightly more concise by grouping common patterns, but the clarity gained from the detailed examples justifies the length. It is front-loaded with the core purpose.

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?

Given the tool's complexity (3 params, nested objects, no output schema), the description covers prerequisites, valid parameter combinations, delivery channel constraints, and return value (subscription id). It does not cover error cases or output schema (not needed). For an agent to correctly invoke this tool, all necessary information is present.

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%, and the description adds significant meaning beyond the schema's brief descriptions. For each type (sec_8k, polymarket_edge, etc.), it provides concrete parameter examples and notes like 'items:["5.02"] = officer change.' For delivery, it details webhook signing and failure auto-disable. This far exceeds what the schema alone conveys.

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 tool's purpose: 'Create a proactive monitoring subscription to a live-data event stream.' It specifies the verb (create) and resource (subscription to event stream). The title 'Subscribe to Alerts' further reinforces this. It distinguishes from sibling tools like list_subscriptions and unsubscribe by implying creation vs listing/removal.

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 explicit guidance on when to use the tool (to set up monitoring) and requirements (Pipeworx OAuth account). It details supported subscription types and their parameters, delivery channels, and links to alternatives like recent_alerts or the registry endpoint. It implicitly advises when not to use it (e.g., anonymous users cannot persist subscriptions).

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