Item contents

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

Annotations state readOnlyHint=false, openWorldHint=true, idempotentHint=false and destructiveHint=false, so the safety profile is already covered. The description usefully signals that 'full' contents (as opposed to stream summaries) are returned, but adds nothing on whether fetching has side effects (consistent with the non-read-only hint) or on output format. There is tension between the word 'Fetch' and readOnlyHint=false, but this mirrors GReader's POST-based item-contents endpoint rather than a clear claim of mutation, so it is not treated as a hard contradiction.

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?

One short sentence with the operation front-loaded and no filler; the GReader parenthetical is the only extra detail and it is immediately useful.

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?

An output schema exists, so return values need no explanation, and one param with no nesting keeps the surface small. Missing is the upstream step for obtaining item ids and any note on cost/batching when passing many ids.

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 single parameter has 0% schema description coverage, so the description must carry the load. It clarifies that the values are item ids and correspond to GReader 'i' parameters, but not accepted form (single string vs array), nor where the ids come from (e.g., freshrss_stream_contents).

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 concrete verb and resource ('Fetch full contents') scoped to 'specific item ids', which implicitly separates it from freshrss_stream_contents (whole-stream listing). It never names a sibling directly, so the differentiation is inferable rather than explicit.

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 when-to-use or when-not-to-use guidance and no named alternative. The agent must guess that this is the follow-up call after stream_contents when full text is needed rather than summaries.

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