fetch_news

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

Beyond the readOnlyHint annotation, the description explains the three action modes and the critical platform limitation (SUSE only for since_update). It adds meaningful behavioral context for a read-only tool, though it doesn't detail return format or error behavior.

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?

Two concise sentences with an action list and platform note. No redundancy, front-loaded with purpose, and every clause adds value.

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 has a simple parameter set and clear annotations. The description covers the main behavior and constraints, but lacks explicit return-value details or examples. Given the schema is thorough and the tool is not highly complex, this is reasonably complete.

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 covers all parameters, giving baseline 3. The description enriches the 'action' parameter by explaining what each action means and adds a key constraint (platform dependency for since_update) that is not in the schema. This extra context justifies a 4.

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 clearly states the tool fetches news from openSUSE and enumerates three specific actions (latest, critical, since_update). It distinguishes itself from sibling tools, none of which are news-related, and provides a specific verb + resource.

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 implies this is the go-to tool for openSUSE news and provides a clear platform constraint (SUSE only for since_update). It does not explicitly name alternatives or exclusions, but the context is clear given the sibling list and the 'Unified news fetching' phrasing.

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