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

Annotations already declare the safe read-only, idempotent, non-destructive profile, so the description only needs to add context. It does: the agent learns the response carries provisional-or-final status, revision history, timestamps, and source URLs, which is meaningful behavioral detail about the data's volatility and provenance.

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 core action and resource; the second sentence is short and additive. The first sentence is long and list-heavy, but every listed field earns its place by describing the payload.

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?

For a zero-required-param, read-only retrieval tool with no output schema, the description covers what comes back (picks, status, revision history, URLs) and how to narrow results. The main omission is routing versus sibling pick tools, which is a usage gap rather than a completeness gap.

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 week/season defaults and the market enum are already fully documented in the schema. The description's 'filter by market' adds nothing beyond that. Baseline 3 is appropriate when structured data does the heavy lifting.

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?

Specific verb (retrieve) plus resource (weekly free ATS/moneyline/Over-Under picks) and a full inventory of the payload (spreads/prices, provisional vs final status, revision history, timestamps, source URLs). The 'free picks' qualifier functionally distinguishes it from the sibling get_member_weekly_picks without needing to name it.

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 only usage cue is 'Filter by market if desired,' which restates the schema default rather than telling the agent when this tool is the right choice. There is no mention of when to prefer it over get_member_weekly_picks, get_member_pick_context, or get_pick_record, and no exclusions.

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