feedbin_list_subscriptions

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 does not state that this is a read-only operation, whether results are paginated, whether all subscriptions are returned or truncated, or what the response looks like. Only the parameter hints are disclosed.

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 short sentences, front-loaded with the action and followed by parameter notes; nothing is padded. It is under-specified rather than bloated, which is a separate concern from structure.

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?

With no annotations, no output schema, and 0% schema description coverage, the definition leaves an agent unable to determine pagination, sort order, or what extended mode returns. For a listing tool in a family of 40+ siblings, this is thin.

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%, so the description must compensate, and it partially does: it reveals the ISO 8601 format for `since` and that `mode` accepts the value "extended" — neither of which appears in the schema, which types both only as nullable strings. However, it never explains what filtering `since` performs or what "extended" changes in the output.

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?

Names a specific verb and resource ("List subscriptions"), which is clearly distinct from siblings like feedbin_get_subscription or feedbin_create_subscription. It stops short of explicitly naming when to prefer it over get_subscription, but the list-vs-get distinction is inferable from the verb.

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 versus the many alternative listing tools (feedbin_list_taggings, feedbin_list_entries) or the single-subscription getter. The word "Optional" hints that params may be omitted, but that is schema restatement rather than usage guidance.

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