feedbin_delete_page

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

No annotations are provided, so the description carries the full burden. "Mutates Feedbin state" does flag that this is a write, but it adds nothing about permanence/irreversibility, whether extracted content is also removed, or whether the operation fails silently on a missing id.

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, with no filler. The second sentence is marginally redundant with the name but still conveys state mutation in a compact form.

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 mutation with zero annotation coverage, no output schema, and an undocumented parameter, the description is too thin. An agent cannot determine safety, prerequisites, or failure behavior from what is written.

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 coverage is 0% for the single parameter page_id, so the description must compensate and does not. It never explains what a page id is, how to obtain one, or what happens with an invalid/nonexistent id.

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 names a specific verb+resource pair ("Delete a saved page") that is unambiguous and clearly distinct from siblings like feedbin_save_page or feedbin_delete_tag. It lacks an explicit sibling comparison, so it lands just short of a 5.

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 page), and no note on where a valid page_id comes from. The only implied usage comes from the word "saved," which the agent must infer.

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