list_subscriptions

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

Despite no annotations, the description declares read-only behavior, handles the empty array case, and notes the API product requirement. This sufficiently informs the agent of the tool's safety and scope.

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?

Two succinct sentences that front-load purpose, return structure, usage context, and constraints. No wasted words.

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 zero-param, read-only tool, the description covers purpose, return format, empty state, usage context, and authorization requirement. Complete and self-contained.

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?

No parameters exist, so the description adds no param details, but it compensates by explaining the return structure (array of objects with id, eventType, callbackUrl, createdAt) and empty result behavior, exceeding the baseline expectation.

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?

Clearly states it returns all active webhook subscriptions with specific fields, distinguishing it from sibling tools focused on activity, sleep, and workouts.

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 mentions using this to audit existing subscriptions before adding new ones, providing practical context. Does not specify when not to use, but the guidance is clear and actionable.

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