get_conference_offense

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

With no annotations, the description carries the burden of disclosing behavior. It states the return format (JSON array) and listed stats, but does not mention potential side effects, rate limits, authorization, or data source nuances. It is adequate for a simple retrieval tool but lacks depth.

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-organized with clear Args and Returns sections. It is succinct, with every sentence contributing useful information, and avoids reduncancy with the schema.

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?

Given the moderate complexity (2 params, one required) and presence of an output schema, the description gives enough context for correct invocation. It could mention error behavior or data source caveats, but for a straightforward stats lookup it is sufficiently 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?

Schema coverage is 0%, yet the description compensates by explaining both parameters: conference with concrete examples ('B12', 'SEC') and season as optional with a default. This adds meaning beyond the bare schema and helps the agent construct valid calls.

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 the tool retrieves conference offensive stats for all teams in a conference, using a specific verb ('Get') and resource ('conference offensive stats'). It lists the specific metrics returned, which distinguishes it from siblings like get_conference_defense.

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 conference-level offensive analysis but does not explicitly mention alternatives or when not to use it. It provides context (all teams, conference code examples) but lacks direct guidance on tool selection versus siblings.

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