feedbin_rename_tag

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

With no annotations, the description carries the entire burden, and it does declare the mutation ('Mutates Feedbin state'), which is useful. However it omits key behavioral facts: whether a missing old_name creates a new tag, whether all taggings are rewritten atomically, whether the operation is reversible, and whether it requires auth scopes.

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, mutation flag front-loaded right after the action, zero filler. It is arguably over-terse rather than padded, but structure-wise it is clean and front-loaded.

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 an unannotated mutation tool with no output schema and 0% schema coverage, the description should cover side effects and failure modes; it covers neither. An agent cannot tell what happens on a nonexistent tag or whether existing taggings survive the rename.

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 both parameters (old_name, new_name) are undocumented except by their titles. The description only implies the old→new mapping by wording; it does not state case sensitivity, format constraints, or whether new_name is validated against existing tags.

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 ('Rename a tag') plus the scope affected ('across taggings'), so the agent knows exactly what changes. It stops short of distinguishing itself from nearby siblings like feedbin_create_tagging or feedbin_delete_tag, which a reader would have to infer.

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 guidance on when to rename versus delete-and-recreate, or when to prefer the tagging-level siblings (create_tagging/delete_tagging). No prerequisites or error conditions are mentioned.

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