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

Annotations already declare readOnlyHint, idempotentHint, and openWorldHint=false, so the safety profile is fully covered. The description adds genuine value by disclosing data provenance (source of each year) and the presence of composite-score worksheets, but says nothing about result size, ordering, or how the year parameter scopes the listing.

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?

A single sentence with the main idea ('Lists every AP exam') front-loaded, followed by the fields it reports. Every clause carries information, though the trailing enumeration is dense enough that it reads as a run-on list of attributes.

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 usefully spells out the returned fields (exams, years, per-year source, worksheet availability), which is the right compensation. The remaining gap is the interaction between the optional `year` filter and the 'years available for each' content, which an agent must guess.

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% and the lone `year` parameter is thoroughly documented there, including the allowed 2024-2026 range and the 2026 default. The description contributes nothing about the parameter and does not clarify whether passing a year narrows the list or the listing always enumerates every available year.

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?

The description uses a specific verb ('Lists') and a precisely scoped resource ('every AP exam with College Board score distributions in this server'), and even enumerates what each entry contains — years, per-year source, and worksheet availability. This reads clearly as a catalog/discovery tool, but it never names a sibling to contrast with, e.g. that per-exam detail lives in get_ap_score_distribution.

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: by describing a complete enumeration of exams and years, an agent can infer this is the discovery step before calling get_ap_score_distribution or estimate_ap_score_from_composite. There is no explicit 'use this when you need to know which exams/years exist' or any exclusion pointing at the estimation or comparison siblings.

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