Subscribe to an RSS feed

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

With empty annotations, the description carries the full burden, and it delivers: immediate fetch behavior, failure on unreachable feeds, SSRF pre-check scope and its version-specific limitation, and side effects like creating and preserving links for feed entries. This is unusually transparent about security and operational caveats.

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?

The description is longer than average, but nearly every sentence carries important behavioral or security information. It front-loads the core purpose and then expands into necessary caveats. A slightly tighter structure could improve readability, but there is little waste.

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?

The description covers behavior, security risks, version-specific behavior, uniqueness constraints, and instance quotas. The main gap is that collection_id and collection_name are optional in the schema, but the description never explains what happens when neither is provided or which default collection is used.

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 schema already covers 100% of parameters with meaningful descriptions, so the baseline is 3. The description adds context about the collection receiving entries and names being unique, but those details are already present or weakly connected to specific parameters. It does not materially improve on the schema's parameter documentation.

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 states a specific verb ('Subscribes to'), a clear resource ('an RSS or Atom feed'), and the core behavior (polling and filing entries as links). This clearly distinguishes it from siblings like create_link and delete_rss_subscription.

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?

It provides clear operational context: this is a subscription tool that polls feeds and preserves each entry as a link. It does not explicitly compare itself to create_link or other siblings, but the behavioral description makes the appropriate use case obvious. Security guidance about untrusted feeds also informs whether to use the tool at all.

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