list_subscriptions

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

No annotations provided; description includes a '[read]' tag indicating it's read-only, and mentions each item is tagged with 'kind'. Does not disclose pagination, auth requirements, or rate limits. Adequate but not detailed.

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?

Single sentence that conveys purpose and result format. No wasted words, front-loaded with key information.

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 simple tool with no parameters and no output schema, description explains the unified list and kind tagging. Could mention pagination, but overall sufficient.

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, input schema empty. Baseline per rules is 4. Description adds no param info but none needed.

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 lists the user's feed follows and webhook subscriptions, distinguishing it from siblings like list_webhooks which shows only webhooks. Verb 'list' and resource 'subscriptions' are specific.

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?

Does not explicitly instruct when to use this vs alternatives like list_webhooks or follow_feed. The context implies it's for a unified view, but no direct when-to-use guidance.

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