Analyze advanced stats for entire roster

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

Annotations already declare readOnlyHint=true, so the description doesn't need to cover that. It adds value by disclosing the batch limit of 10 players and the inclusion of league scoring categories in the response. No contradictions.

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 concise with three sentences, each serving a purpose: stating what it does, how to use it with batching, and what the response includes. No fluff, front-loaded with purpose.

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, the description explains the response includes scoring categories and advises batching. It covers the essential aspects, though it could mention what advanced stats look like per player. Still, it is sufficiently complete for a fetch 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?

Schema coverage is 100% with all parameters described. The description reinforces that playerKeys can be key or name and mentions defaults, but does not add substantial new meaning beyond the schema. Baseline 3 is appropriate.

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 'Fetch advanced stats (Statcast, expected stats, FanGraphs) for a batch of rostered players,' specifying the verb, resource, and type of stats. It distinguishes from siblings like get_roster_stats or analyze_player_stats by focusing on batch analysis and including league scoring categories.

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 explicit instructions: use get_roster to get player keys, split into batches of up to 10, call this tool once per batch, and that calls can run in parallel. It also mentions combining with get_roster to check starting/benched players, giving clear context for when and how to use it.

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