get_latest_news

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 the tool returns real-time news with specific fields (headline, sentiment, categories, sources) and has a limit parameter (1-10), but doesn't mention rate limits, authentication needs, or error behaviors. It adds some behavioral context but leaves gaps.

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 well-structured and front-loaded with the core purpose, followed by return details and parameter guidance. Every sentence earns its place: the first states what it does, the second describes returns, the third explains category usage, the fourth references a sibling tool, and the Args section details parameters without redundancy.

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?

Given 2 parameters with no schema descriptions and an output schema present, the description is mostly complete. It explains parameter semantics thoroughly and notes the output includes sentiment and categories, but doesn't fully address behavioral aspects like error handling or rate limits. The output schema likely covers return values, so this is adequate.

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?

With 0% schema description coverage, the description fully compensates by explaining both parameters in detail. It clarifies that 'category' filters by topic with examples and can be omitted, and 'limit' specifies the number of items with range and default. This adds significant meaning beyond the bare schema.

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's purpose with a specific verb ('Get') and resource ('latest curated crypto news headlines'), distinguishing it from siblings like 'get_news_item' (single item) or 'search_news' (search functionality). It specifies the content type (headlines with sentiment, categories, sources) and real-time nature.

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 clear context for when to use this tool (to get latest headlines) and mentions an alternative ('get_categories first to see all available category codes'), but doesn't explicitly differentiate from other siblings like 'get_enriched_news' or 'get_news_recap'. It gives practical guidance on parameter usage.

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