feedbin_delete_tag

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

With no annotations, the description does carry the key burden of disclosing the cascade ('and its taggings') and labels the operation as mutating Feedbin state. It does not say whether the deletion is reversible, what happens if the tag is absent, or what a successful response looks like — meaningful gaps for an irreversible destructive operation.

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 the cascade behavior; nothing is wasted.

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 trivial one-parameter tool this is close to sufficient, but with no annotations and no output schema, the description leaves the destructive semantics and the meaning of `name` under-specified.

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 `name` parameter has 0% schema description coverage, and the description never explains it — whether it is the tag's literal name versus an identifier, case sensitivity, or matching rules. With only one parameter this is a small but real gap the description should have closed.

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 specific verb and resource (delete a tag) and adds the important scope detail that its taggings are deleted too, which separates it from feedbin_delete_tagging. It does not explicitly point at that sibling, but the resource distinction is legible.

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?

No statement of when to use this versus feedbin_delete_tagging or feedbin_rename_tag, and no prerequisites such as whether the tag must already exist. The agent must infer the choice 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.