get_bill_news_articles

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

No annotations are provided, so the description carries the full burden. It says nothing about ordering, result limits, date filtering, or what the article records contain, leaving the agent with only the bare assertion that news articles are returned.

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 core purpose and usage condition are front-loaded in the first two sentences, and the Args/Returns block is compact. The Returns line is largely redundant with the output schema, but overall the structure is 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?

For a simple read tool with an output schema present, the definition covers the essentials. It is missing details such as result ordering or default page size behavior, which matter for correct pagination usage given take/skip defaults of null.

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, and it does document all three parameters. It clarifies that skip is for pagination and take is the record count, adding meaning beyond the bare integer types in the 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?

States a specific verb and resource ('Get news articles related to a specific bill'), which is clear and distinct from generic siblings. It does not explicitly distinguish itself from adjacent bill tools like get_bill_publications or get_bill_overview, so it falls short of a 5.

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?

Provides clear usage context ('Use when researching media coverage, press releases, or official communications about legislation'), which tells the agent the research intent. However, it names no alternative tools or exclusions, so it stops short of full when/when-not guidance.

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