blog_add_rss

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

No annotations are provided, so the description carries the full disclosure burden. It reveals only that RSS feed generation is 'added', but does not state whether existing files are modified, whether the operation is idempotent, what the API key is used for, or what artifacts are produced. For a mutation-style tool, this is a significant transparency gap.

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 only four words with no wasted text, but this reads as under-specification rather than disciplined conciseness. There is no structuring or front-loading of decision-relevant information, so brevity comes at the cost of usefulness.

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?

Given two parameters, no annotations, and no output schema, the description is severely incomplete. An agent is missing prerequisite context (does a blog need to exist?), the purpose of api_key, and what 'add' means in terms of project changes. The large sibling tool list only increases the need for contextual framing.

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 only 50% (directory is documented, api_key is not), and the description adds nothing about either parameter. An agent cannot determine why api_key is needed, whether it is required in practice, or how it relates to the directory parameter. The description fails to compensate for the schema's gap.

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 ('Add') and resource ('RSS feed generation'), so an agent can tell this tool enables or creates RSS feeds. It is not a tautology of the name, though it adds little beyond what the tool's name already implies and does not specify which blog framework or context it targets.

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?

There is no guidance on when to use this tool versus alternatives. Among the sibling tools, blog_generate_setup and blog_add_seo exist, but the description gives no hint that this is the incremental RSS-specific addition or what prerequisites (e.g., an existing blog project) are required before calling it.

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