Feeds Feed List

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

No annotations are provided, so the description carries the full disclosure burden, and it says nothing about pagination behavior, default page size, auth/permission requirements, or result ordering. "List all feeds" also understates that results are actually paged via page_limit/page_offset, which could mislead an agent into expecting the entire set.

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 single sentence is front-loaded and wastes no words, but its brevity is under-specification rather than effective conciseness. There is nothing to trim, yet also nothing that earns the space it takes.

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?

The tool is simple (zero required params, no nested objects) and an output schema exists, so return values need not be explained. Still, the description omits pagination semantics and any hint about scope, which leaves an agent with a partially incomplete picture for even 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?

Schema description coverage is 0% for both parameters, and the description does not mention page_limit or page_offset at all. The names are suggestive, but neither the description nor the schema explains their semantics (offset units, max page size, or interaction with "all feeds").

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 states a clear verb+resource ("List all feeds"), so an agent immediately knows what the tool returns. However, it offers no differentiation from siblings such as feeds_feed_get, feeds_feed_create, feeds_feed_update, or feeds_feed_delete, which the agent must infer from names alone.

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?

There is no guidance on when to use this list tool versus feeds_feed_get for a single feed or the other feeds_* siblings. Usage is only implied by the verb "list"; no conditions, prerequisites, or alternatives are given.

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