nbl_schedule

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 describes the return structure and fields, but does not disclose behavioral traits like pagination, rate limits, data freshness, ordering, or error handling. The mention of 'seasonType=all' provides one behavioral hint.

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 relatively concise, but the first sentence is a long list of fields. It is front-loaded with purpose and provides a structured return example. Minor verbosity in the field enumeration prevents a perfect score.

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 two-parameter tool with no output schema, the description is fairly complete, explaining the return structure and giving an example. It could be improved by mentioning data ordering, date range, or whether all matches (past and future) are included, but it adequately covers the essentials.

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 has 0% description coverage, so the description adds value by explaining seasonType='all' for the whole season. However, it does not detail the year parameter format, constraints, or valid values beyond 'one season'. The description partially compensates for the lack of schema descriptions.

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 'every match for one season' with detailed fields, distinguishing it from sibling NBL tools like nbl_ladder (standings) or nbl_match_outcomes (specific outcomes). The verb 'returns' and resource 'season schedule' are specific.

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 retrieving a full season schedule and includes the seasonType parameter, but does not explicitly mention when to use this tool versus alternatives like nbl_next_matches or nbl_season_current. No exclusions or context are provided.

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