get_feed

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

With no annotations provided, the description carries the full burden. It discloses that articles are pre-scored, classified by political lean, topic, country, audience, and de-duplicated. This adds context beyond the schema, though it does not mention return format or pagination.

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 moderately long but well-structured with a brief intro followed by a parameter list. Each line adds value without unnecessary fluff. It could be slightly more concise, but it is effective.

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?

All 8 parameters are thoroughly documented. Despite lacking an output schema, the description explains the article enrichment (scoring, classification). It is complete for the tool's purpose, though it omits specifics on response structure like pagination.

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%, but the description provides detailed explanations and allowed values for all 8 parameters. For example, it lists all topics, political leans, audience types, and gives usage hints like 'min_score: Use 7+ for breaking-only'. This greatly aids an AI agent in selecting correct parameter values.

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 retrieves a filtered feed of enriched news articles, with specific verb 'Get' and resource 'feed'. It distinguishes from siblings like 'get_breaking' and 'search_news' by emphasizing pre-scored, classified, and de-duplicated articles.

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 provides implied usage context (e.g., 'Use 7+ for breaking-only') but does not explicitly state when to use this tool versus alternatives like 'get_breaking' or 'search_news'. No direct guidance on when not to use it.

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