Subscribe to an RSS feed

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

Since annotations are empty, the description takes on full disclosure responsibility. It reveals key behaviors: immediate fetch for validation, uniqueness constraint per account, default subscription cap, and that entries are preserved per account defaults. No contradictions.

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 paragraphs, each with a single cohesive idea: first explains what the tool does, second details constraints and immediate effects. No filler, every sentence adds essential information.

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?

Covers all key aspects for a creation tool: what it does, immediate behavior, constraints (names, cap), and how feeds are processed. Lacks output schema or mention of return values, but given the tool's nature (void-like creation), the description is adequately complete.

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 covers all 4 parameters with descriptions, but the description adds value by explaining the overall behavior (e.g., immediate fetch, uniqueness, cap) that the schema alone does not convey. The mutual exclusivity of `collection_id` and `collection_name` is left to the schema.

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 clearly states the tool subscribes to an RSS or Atom feed and explains what Linkwarden does with it (polls and files entries). It also distinguishes from sibling tools like `delete_rss_subscription` by focusing on creation.

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?

Provides explicit usage context such as immediate fetch behavior, uniqueness requirement for names, and account caps on subscriptions. It does not explicitly mention when not to use it or compare to alternatives, but the context is clear enough for proper use.

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