feedbin_delete_saved_search

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

With no annotations present, the description carries the full disclosure burden. "Mutates Feedbin state" does flag that this is a write, but a delete tool needs more: whether deletion is permanent, what happens to an invalid or already-deleted search_id, and whether any auth scope is required are all unstated.

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 compact sentences with the operation front-loaded; nothing is padded or buried. The second sentence is thin but does carry the one behavioral fact present.

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 one-parameter tool with no annotations and no output schema, the description omits the essentials: irreversibility, success/failure behavior, and the provenance of search_id. What is there is accurate but far short of what an agent needs to call this safely.

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% and the single parameter (search_id) is undocumented in both schema and description. The description never says the id comes from feedbin_list_saved_searches or that it must be an existing saved search, so nothing compensates for the coverage gap.

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?

States a concrete verb and resource ("Delete a saved search") that unambiguously separates it from the create/update/get saved-search siblings. It stops short of naming which sibling to use if the intent was something else, but the operation itself is unmistakable.

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 feedbin_update_saved_search or feedbin_delete_tag, no preconditions, and no warning about irreversibility. The agent must infer all usage context from the tool name alone.

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