whats_new

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

With no annotations provided, the description only adds the credit cost as behavioral context. It does not disclose read-only nature, side effects, or other traits beyond the cost. For a simple retrieval tool, this is adequate but not comprehensive.

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 sentences, zero waste. The first sentence covers purpose, the second gives usage context. Information is front-loaded and efficient.

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 description lists content types but omits output format details. With no output schema, the agent lacks guidance on return structure. For a tool with 2 simple parameters and a clear brief, this is acceptable but not 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?

The schema already describes both parameters (days, news_limit) with clear defaults and ranges. The description adds no further details, so it meets the baseline for 100% schema coverage.

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 explicitly states the tool provides a morning brief covering pricing changes, new/removed models, status incidents, and top news. This specific verb+resource combination clearly distinguishes it from siblings like get_ai_news or get_ai_today.

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 advises 'the tool to call when your agent boots up,' giving clear context for use. It also mentions cost (1 credit). However, it does not explicitly exclude scenarios or name alternatives, leaving some ambiguity.

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