list_feeds

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

With no annotations, the description carries full responsibility for disclosing behavior. It only states 'List all feed subscriptions,' which implies a read-only operation but does not mention return format, pagination, ordering, or side effects. This is minimally transparent for a listing tool.

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 a single, clear sentence with no superfluous words. It is perfectly concise and front-loaded, stating exactly what the tool does without any filler.

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 no parameters, no annotations, and no output schema, the description is minimally viable. It lacks information about return fields, whether all feeds are returned at once, or any limits. The presence of sibling tools like get_feed_groups suggests more context could be useful, but the description is not grossly incomplete for a simple list operation.

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?

The tool has zero parameters, so the schema is trivially 100% covered. The description does not need to explain parameter meaning, and the baseline for zero-parameter tools is 4. No additional information is required.

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 'List all feed subscriptions' uses a specific verb ('list') and identifies the exact resource ('feed subscriptions'). It clearly distinguishes from siblings like get_feed_items or get_unread, which focus on items or unread counts.

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?

No guidance is provided on when to use this tool versus alternatives. There is no mention of what differentiates it from get_feed_groups or get_items, and no exclusions or context. The implied usage is simply to list feeds, but no explicit direction is given.

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