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

Annotations already declare readOnlyHint=true, idempotentHint=true, and destructiveHint=false, so the safety profile is covered. The description adds useful domain semantics for leverage_gap (above 0 = field owns the stack less than its boom rank) but says nothing about pagination, plan limits, or how 'today' and the default slate interact.

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?

Front-loads the resource ('Team stack board for today') and puts the leverage_gap interpretation in a compact second sentence. The metric enumeration is long but each item maps to a returned column, so it earns its place.

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?

There is no output schema, so the description must convey what comes back, and it does by listing the returned metrics. Remaining gaps are minor: no mention of row ordering defaults (sort_by is optional with no stated default) or how limit interacts with the plan limit.

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 description coverage is 100%, so all five parameters are already documented in the schema; baseline 3 applies. The description's leverage_gap note adds interpretation for one sort_by enum value but no syntax, format, or per-parameter behavior beyond the schema.

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 the resource precisely ('Team stack board for today') and enumerates the metrics it returns (TeamROO score, implied/expected runs, boom/bust chance, ceiling runs, opposing starter, ownership). This lets an agent distinguish it from siblings like invoke_mlb_optimizer or invoke_mlb_ownership_by_contest, though the verb is only implicit ('board', not 'returns/lists').

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?

No when-to-use or when-not guidance and no alternatives named. 'For today' and the leverage_gap definition imply context, but nothing tells the agent when this board is preferable to invoke_mlb_sim_picks, invoke_mlb_optimizer, or invoke_nfl_team_stacks (the sibling variant).

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