feedbin_delete_subscription

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

With no annotations, the description carries the full burden. "Mutates Feedbin state" correctly signals a write, but says nothing about irreversibility, whether the operation is idempotent, what happens if subscription_id does not exist, or what is returned.

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 terse sentences with no wasted clauses, which is good, but the brevity comes at the cost of substance rather than being efficiently front-loaded 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 destructive single-parameter tool with no annotations and no output schema, the description should at minimum identify the resource being deleted and the effect on the feed/entries. Neither is covered.

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 single parameter subscription_id has 0% schema description coverage, and the description does not mention it at all — no statement of where to obtain the id, whether it is the Feedbin subscription id versus a feed id, or what happens with an invalid value.

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?

"Unsubscribe" is a specific verb, but the description never names the resource (a subscription) or clarifies that it removes a Feedbin subscription, leaving the tool name to carry that meaning. Against siblings like feedbin_delete_tag and feedbin_delete_page the verb alone does not disambiguate.

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 alternatives, no prerequisites (auth, ownership of the subscription), and no note on whether feedbin_update_subscription could achieve a similar outcome. Usage is only implied by the tool name.

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