Subscribe

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

Annotations already declare the key traits (write, non-idempotent, open-world, non-destructive), and the description adds no behavioral context beyond them. It does not mention duplicate handling, authentication, or rate limits, though the annotations cover the safety profile.

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?

A single, front-loaded sentence with no wasted words; every part (feed, optional title/category) earns its place.

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 simple 3-parameter write tool with output schema and annotations, the description covers purpose and optional fields, but it omits required-parameter emphasis and duplicate-subscription behavior. It is minimally adequate but leaves clear gaps.

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 the description must compensate, but it only names title and category as optional and never mentions feed_url or parameter formats. This adds marginal meaning beyond 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?

States a specific verb 'Subscribe' and resource 'feed,' and the optional title/category scope is clear. The action is inherently distinct from sibling unsubscribe, so an agent can route correctly.

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 no explicit when/when-not guidance or alternatives (e.g., freshrss_ingest_subscriptions). Usage is only implied by the tool name, which is insufficient for distinguishing ingestion vs manual subscription.

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