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

Annotations flag destructiveHint=true and openWorldHint=true; the description adds that the fetch causes new items to be posted according to post mode, which is the concrete side effect an agent needs to understand before triggering. It also discloses the posts.draft permission requirement and 404 behavior for foreign ids. Only missing detail is whether the reschedule is reversible/undoable.

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?

Four short, front-loaded sentences: action, side effect, when to use, verification step, error case, permission. Each sentence carries distinct information with no repetition of the name or title.

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?

With an output schema present, return values need not be explained. The description still covers timing, side effects, error behavior, follow-up, and permissions, leaving nothing material for an agent to guess before invoking.

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 coverage is 100%, so both id and workspaceId are already documented in the schema, including sourcing and workspace consistency rules. The description adds only the 404 behavior for out-of-workspace ids, which is marginal incremental value over the schema baseline.

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 and resource ('Move an RSS feed's next check to now') with immediate effect spelled out (fetched within a minute, items posted per post mode). This clearly distinguishes it from pause_rss_feed, resume_rss_feed, and preview_rss_feed siblings.

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?

Explicitly names the triggering situation ('when the user just published an article and does not want to wait for the interval') and the follow-up action ('Read list_rss_feed_items a minute later'). This gives when-to-use, an alternative-avoidance rationale, and the next step.

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