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

Annotations already declare readOnlyHint, idempotentHint, and non-destructive, so the safety profile is covered. The description adds genuinely useful context beyond that: this is a member-gated published board with fixed content rather than generated output, and it tells the agent what is included (exact spreads, recorded odds, confidence). Return format details remain absent.

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 short, front-loaded sentences that lead with the audience gate and the resource, then the contents, then the exclusion. The middle clause about spreads/odds/confidence is informative rather than filler, and nothing is redundant.

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 no output schema, the description correctly compensates by summarizing returned content (spreads, odds, confidence), and annotations cover the safety profile. Member-gating and read-only behavior are both addressed; only edge cases like empty boards or unpublished weeks go unmentioned.

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%, with each of the three parameters documenting its meaning and default, so the baseline is 3. The description echoes the market dimension ('ATS, moneyline, and Over/Under') but adds no syntax or format detail 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 a specific verb and resource — retrieve the full published ATS, moneyline, and Over/Under board — plus a negative scope statement ('Does not generate fresh predictions'). Gating is signaled by 'Active members,' which implicitly separates it from get_weekly_free_picks, but that sibling is never named, so the differentiation is inferential rather than explicit.

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?

Gives clear context for use ('Active members... to discuss with your AI') and an explicit exclusion ('Does not generate fresh predictions'), so the agent knows this is a retrieval-only tool for analytical discussion. It falls short of 5 because it never names the free or record-lookup alternatives it overlaps with.

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