feedbin_create_tagging

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

With no annotations, the description carries the full disclosure burden, and "Mutates Feedbin state" only confirms a write. It says nothing about idempotency, what happens if the same tag is applied twice, whether it overwrites or adds, or what identifiers are needed to target the write.

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. Brevity is achieved, though the space saved is not spent on anything useful.

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?

A mutation tool with no annotations, no output schema, and fully undocumented parameters needs considerably more than this. Key facts an agent would need before calling it are absent.

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 neither parameter (feed_id, name) is mentioned or explained. 'Tag a feed' weakly implies a feed identifier and a tag string, but that inference is not drawn out, so the agent gets no meaning beyond the bare JSON keys.

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 verb-and-resource pair "Tag a feed" identifies the operation, but with siblings like feedbin_rename_tag and feedbin_list_taggings the agent cannot tell from this text whether it creates a new Tag entity, attaches an existing tag to a feed, or replaces existing taggings. The name 'create_tagging' implies an association object, which the description never makes explicit.

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 use this versus feedbin_rename_tag or feedbin_list_taggings, and no stated preconditions such as the feed or tag needing to exist. The two sentences give context for nothing beyond the operation itself.

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