freshrss_get_article_detail

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

No annotations are provided, so the description carries the full behavioral burden. It does disclose a meaningful constraint: 'Max 10 articles per call to control token usage.' However, it does not mention auth prerequisites, behavior for invalid/unknown IDs, or any rate-limit implications, leaving some behavioral uncertainty.

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?

Three short sentences, each earning its place: purpose, usage timing, and an important limit. The key information is front-loaded, and there is no redundant or vague wording.

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 tool is simple, has an output schema, and the description covers what the tool does, when to use it, and the key parameter constraint. The only minor gap is that it does not explicitly state that article IDs come from headline-scanning tools, though the usage sentence strongly implies this workflow.

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. It does by naming the key parameter concept ('specific articles by ID') and by stating the max of 10 articles per call, which matches the article_ids parameter. It could additionally explain where IDs come from, but for a single-parameter tool this is sufficient.

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 action and resource: 'Get full content for specific articles by ID.' This clearly distinguishes the tool from siblings like freshrss_get_headlines, which only provide headline-level content, making it easy for an agent to select the right tool.

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?

The description explicitly says 'Use after scanning headlines to deep-dive into interesting articles,' providing clear workflow context. It does not explicitly name alternatives or exclusions, but the intended use case is unambiguous given the sibling tools.

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