get_kpoy

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

With no annotations, the description adds that the response is a JSON array possibly containing multiple tables and that Game MVP data starts from 2013, which are useful behavioral traits beyond what the name suggests. It doesn't address auth or rate limits, but for a read-oriented stats tool, the provided context is reasonable.

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 brief and front-loaded with the purpose, followed by return type and parameter semantics. Every sentence contributes essential information without redundancy.

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?

The tool is simple with one optional parameter; the description covers purpose, return format, and parameter behavior, sufficient for selection and invocation. The existing output schema further reduces the need for detailed return explanations.

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 input schema only lists 'season' with no description, but the description fully explains the format ('2024'), default current season, earliest year 2011, and MVP table restriction, completely compensating for zero schema coverage.

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 opens with a specific verb and resource ('Get KenPom Player of the Year standings') and clarifies it returns both KPOY leaderboard and Game MVP leaders, which clearly distinguishes it from sibling stats tools.

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?

No explicit alternatives or when-not-to-use instructions are provided, but the description implies this tool is for KPOY data. The parameter notes on season defaults and earliest availability offer some usage context.

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