List probable starting pitchers for a date

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

Adds significant behavioral details beyond readOnlyHint annotation: data source (MLB Stats API, no Yahoo auth), date availability, output format (compact row table with columns), fantasyContext enrichment behavior including performance warning (~10-26 requests). No contradiction with 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?

Information-dense but well-structured: front-loaded with main purpose, then date availability, then output format, then fantasyContext. Slightly long but every sentence adds value, earning a 4.

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?

Thoroughly explains output structure (columns and row format) in absence of output schema, covers both parameters with usage nuance, and addresses performance concerns. Complete for a 2-parameter, no-output-schema tool.

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?

Both parameters are fully described in schema (100% coverage), but description adds valuable context: default date behavior with planning tips, fantasyContext explanation of added fields and performance trade-off.

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?

Explicitly states it lists every probable starting pitcher for a date with clear resource (starting pitchers) and verb (list). Distinguishes from siblings like list_games or list_players by focusing on probable starters.

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?

Provides clear context on when dates are valid (today through ~2-3 days out) and explains that far-out dates return few results (not an error). Lacks explicit 'when not to use' or alternative tools, but the date guidance is strong.

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