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

With no annotations, the description carries full burden for behavioral disclosure. It states the tool returns 'real-time' news with specific fields and is 'curated'. It does not mention authentication, rate limits, ordering, or what happens when no news is available. The description adds some value beyond the schema but lacks depth on behavioral traits.

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 appropriately sized, with the main purpose front-loaded. The Args section is structured and readable. One minor inefficiency: the category documentation appears twice (in prose and in Args), but overall it is concise and well-organized.

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 the tool has an output schema (not shown), the description is not required to detail return values. It mentions headline, sentiment, categories, sources. Two parameters are fully explained. It covers the main use case (getting latest filtered news) but omits edge cases (e.g., empty results, error handling) and does not clarify ordering ('latest' is vague but acceptable for a simple list tool).

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 adds clear semantic meaning: category filter with examples (bitcoin, defi, ai), limit range (1-10) with default (5), and effect of omitting category. This goes well beyond what the schema provides (only type/default).

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 'Get the latest curated crypto news headlines' with specific return fields (headline, sentiment, categories, sources). It distinguishes itself from sibling tools like get_categories by recommending calling get_categories first, and from get_news_item/get_enriched_news by implication (latest headlines vs detailed items).

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 explicit guidance on using the category parameter and advises calling get_categories to see available codes. It explains when to omit category for all news. However, it does not explicitly contrast usage with other siblings like get_enriched_news or get_news_recap, so guidance on alternative tools is limited.

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