Get team roster with stats

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

Annotations provide readOnlyHint=true, and description adds context about being 'heavier' than get_roster, implying more data retrieval. No destructive behaviors or contradictions. Does not discuss rate limits or auth, but sufficient given annotations.

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?

Three sentences, front-loaded with the core action, followed by comparisons and defaults. No superfluous words; every sentence adds value.

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 no output schema and low complexity (2 optional params), the description adequately covers purpose and defaults. Could be more specific about which stats are returned ('Yahoo stats' is vague), but sufficient for selection and invocation.

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 covers both parameters with descriptions (100%). Description adds default behavior context: 'Defaults to the configured team and today's date,' which is not fully captured in schema. Provides useful nuance beyond parameter names.

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 'Get a team's roster with each player's Yahoo stats for a given date,' providing a specific verb and resource. It distinguishes from siblings by naming 'get_roster' and 'analyze_roster_stats' with clear differentiation.

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?

Explicitly advises when to use alternatives: 'use get_roster when you only need slots/status, or analyze_roster_stats for advanced stats.' Also notes defaults for date and team, guiding correct usage.

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