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

Annotations already declare readOnlyHint=true and openWorldHint=true, so the safety profile is covered. The description adds that the source is MLB Pipeline's curated rankings and that values come from mlb_discovery, but says nothing about pagination behavior, freshness, or rate limits beyond what the schema already encodes.

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 sentences, front-loaded with the available ranking views and followed by filter dimensions and the discovery pointer. Efficient with little waste, though the filter list slightly duplicates the schema.

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?

With an output schema present, return values need no explanation, and the view-dependent required parameters are covered in the schema. The description covers the five views and the discovery dependency, but omits how this tool relates to mlb_prospect_stats for an agent choosing between them.

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%, so every parameter is already documented in the schema. The description restates the filter dimensions (year, team slug, position, name, sort, pagination) and points to mlb_discovery for valid values, adding marginal value over the structured fields. 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?

States a specific verb (Fetch) and resource (MLB Pipeline's curated rankings) and enumerates the exact ranking variants available (Top 100, Top 30 by Team, Top 10 by Position, Draft Top 200, International Top 50). This clearly distinguishes it from siblings like mlb_prospect_stats (stats) or mlb_player (player profiles).

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?

It routes the agent to mlb_discovery for accepted values, which is useful, but gives no guidance on when to choose this over mlb_prospect_stats or other MLB tools, nor any prerequisites. Usage is implied rather than stated.

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