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

No annotations are provided, so the description carries the full burden. It discloses ordering (by confidence score) and a workflow prerequisite, but says nothing about pagination, result limits, whether candidates persist between calls, or that this is a non-mutating read. Adequate for a simple list tool, but not rich.

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?

Three short sentences, zero waste. The primary action is front-loaded, the prerequisite follows, and the filter hint comes last.

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 one-parameter list tool with no output schema and no annotations, the description covers what the tool returns conceptually (candidates ranked by confidence), the prerequisite to populate them, and how to filter. It stops short of describing candidate fields or volume behavior, but an agent has enough to call it 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 description coverage is 100% and the single enum parameter is fully documented in the schema. The description restates the filter and its values (pending, accepted, dismissed) without adding syntax or behavior beyond what the enum already conveys, so the baseline 3 applies.

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?

States a specific verb (List) and resource (auto-detected subscription candidates) with the ordering criterion (confidence score). It is immediately distinguishable from detect_subscription_candidates (which generates) and get_subscriptions (which lists actual 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?

Explicitly names the prerequisite tool ('Call detect_subscription_candidates first to generate fresh candidates') and explains the purpose of the status filter. It does not call out when to prefer this over get_subscriptions or get_subscription_by_id, but the workflow dependency is the key guidance and it is stated.

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