nbl_news

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

No annotations are provided, so the description should disclose behavior. It mentions the response is a raw array of ~200 articles and lists fields, but does not discuss side effects, rate limits, or behavior when limit is omitted.

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?

Description is reasonably concise and front-loaded with the tool's purpose. However, the extensive list of fields adds some verbosity; could be slightly more concise without losing clarity.

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 news retrieval tool with one parameter and no output schema, the description covers the main aspects: data fields, response format, and a usage example. Missing minor details like default limit behavior, but overall complete enough.

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 coverage is 0%, and the description only states 'Use limit to cap rows.' No details on default value, range, or null behavior. The example 'Latest 10 NBL articles' implies usage but doesn't fully compensate for missing schema documentation.

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?

Clearly states it returns NBL news articles with a rich set of fields (title, body, excerpt, etc.). Differentiates from sibling NBL tools like nbl_ladder or nbl_match_outcomes by focusing on news content.

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 guidance on using the 'limit' parameter and warns about the raw array response format. However, does not specify when to use this tool versus alternatives or when not to use it.

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