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

Annotations already declare readOnlyHint=true, so no repetition is needed; the description adds that the document mirrors the athlete's Profile page and that the grade block is machine-read and scopes every knowledge-base search. This goes beyond the annotation's binary safety flags and clarifies content semantics.

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 sentences, each with a distinct purpose: state the output, position it against `list_facts`, and flag the machine-read grade block. No wasted words, and the main function is front-loaded.

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 no-parameter, read-only tool, the description covers its purpose, relationship to the structured alternative, and a key behavioral detail (grade-block scoping). The absence of an explicit output format is a minor gap, but the term 'document' and the reference to the Profile page convey the essential return nature.

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 tool has zero parameters, so the baseline for this dimension is 4; the description adds no parameter-specific meaning because none exist, but clarifies that the `grade` block (sport/level/populations) is machine-readable, which is output context rather than parameter semantics.

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 tool's function as rendering everything known about an athlete as a single document, and explicitly contrasts it with `list_facts`, distinguishing the two. The mention of the grade block scoping knowledge-base searches adds precision.

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?

Directly instructs when to use this tool ('Kept for readers that want it in one piece') and names `list_facts` as the alternative for structured needs (ids, states, single area). It also warns that the grade block scopes knowledge-base search, helping an agent decide based on query intent.

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