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

Annotations already declare readOnlyHint, idempotentHint, destructiveHint=false and openWorldHint, so the safety profile is fully covered by structured data. The description's only behavioral addition is scope ("for all teams"), which is real but thin; nothing is said about data freshness, caching, or whether the standings are live or end-of-day.

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?

Two short sentences, front-loaded with the purpose before the field list, and no filler. The field enumeration in sentence two overlaps with the output schema, so it is slightly redundant rather than wasted, which keeps this just below the top 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?

A zero-parameter read tool with an output schema and rich annotations has little left to explain, and the description covers purpose and scope adequately. The only genuine gap is the lack of any cue distinguishing it from the other nhl_* retrieval siblings.

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 tool takes zero parameters, so there is no parameter meaning for the description to carry and the schema-coverage baseline of 4 applies. The description correctly avoids inventing input options such as season or conference filters that the schema does not support.

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?

"Check current NHL standings" pairs a specific verb with a specific resource, and the second sentence enumerates the fields returned, so the agent knows this is a league-wide standings snapshot. It never explicitly contrasts itself with nhl_get_scores or nhl_get_schedule, so the differentiation is left to the resource noun alone rather than stated.

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 word "current" implies this is for present-season standings rather than historical lookups, which is a usable cue. There is no explicit when-to-use, when-not-to-use, or named alternative (e.g. use nhl_get_scores for individual game results), so routing is inferred rather than guided.

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