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

Annotations already declare readOnlyHint=true and openWorldHint=true, so safety is covered. The description adds only the hint that the metadata is 'stable' (i.e. largely static/cacheable), which is mild but genuine behavioral context; no auth, rate-limit, or freshness details are given.

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?

It is a single short, front-loaded fragment, so there is no padding. But the brevity comes at the cost of under-specification rather than efficient information density.

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?

An output schema exists so return values need not be described, but with three required undocumented parameters and no usage or scope guidance, the definition is too thin for an agent to call it confidently.

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?

All three parameters (team_id, sport, slug) are required with 0% schema description coverage, and the description says nothing about their meaning, format, or relationship. It neither explains the identifiers nor clarifies whether sport/slug are filters or keys, leaving the schema gap unmitigated.

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 names the resource (team) and scopes it to one team, which loosely separates it from the plural sibling draftkings_teams. However, it lacks a clear verb (retrieve/fetch) and the phrase 'stable metadata' is vague jargon, so an agent cannot be fully certain what is returned.

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?

There is no when-to-use guidance and no reference to alternatives such as draftkings_teams, draftkings_league_events, or draftkings_event_context. The agent must infer the invocation context entirely.

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