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

Annotations already declare readOnly, idempotent, non-destructive, closed-world behavior, so the safety profile is covered. The description adds real value beyond them by disclosing the shape of the result — overall record, breakdown by prediction type, and contributor count.

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?

One front-loaded sentence with a colon-delimited list of the aggregate dimensions; no filler. The dependent clause 'aggregated across everyone writing or speaking under its banner' is slightly wordy but still earns its place by defining the aggregation.

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 single-parameter read tool with no output schema, the description adequately conveys what comes back (overall record, per-prediction-type splits, pundit count). The main residual gap is routing guidance against the many sibling record/leaderboard tools.

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?

The single parameter is fully documented in the schema (outletSlug, sourced 'from find_entities'), and the description adds nothing about it. With 100% schema coverage and one param, the baseline 3 applies.

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 resource and scope: 'One publication's NFL record, aggregated across everyone writing or speaking under its banner.' The phrase 'one publication's' implicitly separates it from sibling pundit_record (one person's record), but no sibling is named explicitly, so it falls short of full differentiation.

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?

Usage is only implied: an agent can infer this is the outlet-level aggregate versus pundit_record, leaderboard, or list_takes, but the description never states when to choose this tool over those alternatives or what prerequisites apply.

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