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

Discloses auth requirement ('Requires a Pipeworx OAuth account'), phone verification and SMS cap, and return value. Annotations (idempotent, readOnly=false) already set safety expectations; description adds operational constraints. No contradiction with annotations.

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?

Description is front-loaded with purpose and return value, then covers auth, types, and delivery in a structured way. It is longer than the ideal but every sentence adds necessary detail for a multi-type subscription tool.

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?

Tool is complex (3 params, nested objects) with no output schema; description covers return value, authentication, supported types (partially), and delivery options. The schema fills gaps for remaining types and webhook details, making the description sufficient.

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%, so baseline 3. The description adds value by providing concrete examples for sec_8k (items:['5.02']), polymarket_edge (topic:'fed'), and fred_series (series_id:'UNRATE'), and explaining delivery channel syntax. It omits two types from description but schema covers them.

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 states 'Create a proactive monitoring subscription to a live-data event stream' and 'Returns the new subscription id', clearly defining the action and output. It distinguishes from sibling tools like list_subscriptions and recent_alerts by focusing on the creation of subscriptions.

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?

Provides context for when to use: 'proactive monitoring' and mentions pulling alerts via 'recent_alerts or GET registry.pipeworx.io/alerts.json', implying an alternative for one-off retrieval. However, it doesn't explicitly say 'use recent_alerts instead' or exclude cases like one-time data needs.

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