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

Annotations already declare readOnlyHint and openWorldHint. The description adds behavioral context beyond that: the subscription activates automatically after payment, the checkout_url requires no DripRaven login, and the return object varies based on the plan parameter. It doesn't contradict annotations; it enriches them with operation-specific details.

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 well-structured, starting with the primary directive 'Prefer this' and then explaining both branches of behavior. Every sentence adds value—use case, return differences, activation, and the sibling comparison. It is concise for the amount of information delivered.

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 single-optional-parameter tool with no output schema, the description fully explains return formats, the decision logic, post-payment behavior, and how it relates to send_broadcast and billing_status. No critical information is missing for an agent to call this 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% and the schema already describes the plan parameter well. However, the description adds meaning by explaining how different plan values affect the returned object (subscribe_url vs checkout_url) and the exact semantics of omitting it, which goes beyond the schema's brief description.

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 obtains a subscription link for the user, and distinguishes it from siblings like billing_status by explaining that this returns a checkout link while billing_status returns plan details. It specifies the exact resource (subscribe_url vs checkout_url) and the conditions for each, making it unambiguous.

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 gives explicit when-to-use guidance: hand the user subscribe_url by default, pass plan only when the user has chosen a tier. It also names an alternative (billing_status) for describing plans in chat, and instructs to retry send_broadcast after subscription activates. This fully covers decision-making for the agent.

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