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

The description adds significant behavioral context beyond annotations: OAuth account requirement, phone verification, SMS daily cap, webhook auto-disabling after failures, and one-time signing secret. These are meaningful operational details that help an agent anticipate side effects and prerequisites.

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 dense but well-structured: purpose → requirements → types → delivery channels. Every sentence carries useful information, though it is relatively long. It avoids redundancy and is front-loaded with the core action.

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 tool with nested params, no output schema, and several caveats, the description covers prerequisites, each subscription type with example params, delivery options with security details, and return value (subscription id). It is thorough and self-sufficient for an agent to invoke 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 baseline is 3. The description still adds value by giving concrete examples and semantic hints (e.g., items:["5.02"] = officer change, 'cross-venue mispricings'), enriching the parameter understanding beyond the schema's formal definitions.

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 explicitly states 'Create a proactive monitoring subscription to a live-data event stream' and mentions returning the new subscription id. This is a specific verb+resource pair that clearly distinguishes the tool from siblings like 'list_subscriptions' and 'unsubscribe'.

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 usage context: requires a Pipeworx OAuth account, explains supported types with examples, and describes delivery channels. However, it does not explicitly contrast with alternative tools (e.g., when to use 'recent_alerts' instead of subscribing), so it lacks explicit exclusions.

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