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

Beyond the annotations (readOnlyHint=false, idempotentHint=true, etc.), the description discloses significant behavioral traits: auth persistence requirements, always-on feed behavior, SMS verification and 10/day cap, webhook signing secret returned once, and auto-disable after 10 failures. These details go well beyond what annotations provide, giving agents a clear picture of side effects and constraints. No contradiction with annotations found.

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 long but well-structured: it front-loads the purpose and return value, then organizes supported types and delivery channels into clear sections. Each sentence adds necessary operational detail. While it could be trimmed slightly (e.g., some redundancy with the schema), the density of useful information justifies the length.

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 high complexity (nested objects, multiple types, optional delivery channels) and the absence of an output schema, the description is remarkably complete. It covers return values, auth requirements, type-specific parameters, delivery options, verification steps, rate limits, and failure behavior. This effectively compensates for the missing output schema and provides agents with enough context to invoke the tool correctly.

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 the baseline is 3 per the rubric. The description adds extra semantic value by mapping item codes to meanings (e.g., items:['5.02'] = officer change) and providing concrete examples for each subscription type. It also clarifies delivery constraints (phone verification, caps) that aren't fully detailed in the schema, so it adds genuine meaning beyond the structured fields.

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 opens with a specific verb+resource: 'Create a proactive monitoring subscription to a live-data event stream.' It clearly states the primary action and distinguishes this from sibling tools like list_subscriptions and unsubscribe by focusing on creation. Returning the new subscription id is also mentioned, reinforcing the tool's purpose.

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 for when to use the tool (proactive monitoring), prerequisite auth requirements (Pipeworx OAuth account), and detailed examples for multiple subscription types. However, it does not explicitly contrast with alternatives like recent_alerts or list_subscriptions, leaving some implicit guidance around when to choose this vs. other monitoring or retrieval tools.

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