nhl_get_draft

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

No annotations are provided, so the description must convey behavioral traits. It only states the tool gets 'current' data, but fails to clarify whether this is live, cached, or how often it updates. There is no mention of mutability, authentication, or rate limits. The description lacks sufficient disclosure for safe agent invocation.

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 a single sentence with nine words, immediately front-loading the verb and resource. Every word adds value, making it highly efficient and easy to parse.

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 tool has no parameters, no output schema, and no annotations, the description is sufficient to understand its basic function. However, it lacks details about the structure of the returned data (e.g., ranking format, prospect fields), which an agent might need to effectively use the output.

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?

There are no parameters in the input schema, so schema description coverage is trivially 100%. With zero parameters, the baseline is 4, and the description does not need to add parameter details. It correctly implies no inputs are required.

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 the current NHL draft rankings and prospect information. It uses a specific verb ('Get') and resource, and it distinguishes itself from sibling tools which focus on games, players, schedules, and standings. No other sibling tool covers draft data.

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 provides no guidance on when to use this tool versus alternatives. It does not mention context like draft season or time relevance, nor does it exclude any scenarios. Agents receive no explicit direction on appropriate usage.

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