nbl_news

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

Beyond the annotations (read-only, idempotent, open world), the description adds crucial behavioral context: it returns a raw array rather than an envelope, defaults to ~200 articles, and states 'Auth: none needed.' This enriches the agent's understanding of what to expect.

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 with a clear opening, a returns section, an example, and an auth note. It is slightly redundant (field list appears twice), but the content is relevant and front-loaded, so it earns a 4.

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?

Despite lacking an output schema, the description provides a full breakdown of the return fields, an example call, the raw array format, and authentication requirements. It fully describes the tool's behavior and the single parameter, making it complete 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?

The schema already provides a complete description of the `limit` parameter, including default behavior. The description repeats this ('Use `limit` to cap rows') and gives an example, but adds no new semantic meaning beyond the schema. Baseline 3 is appropriate.

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 it returns NBL news articles, which is a specific resource. It lists the exact fields and notes the raw array format, making the tool's purpose unambiguous and distinct from other news-related siblings by its NBL scope.

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 implies usage for fetching latest NBL news but does not explicitly compare with alternatives or state when not to use the tool. The only guidance is to use `limit` to cap rows, which is more parameter usage than tool selection guidance.

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