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

Annotations already declare readOnlyHint, idempotentHint, destructiveHint=false and openWorldHint=false, so the safety profile is covered. The description adds that results are 'ordered' and that the takes are reusable by design, which is modest but genuine context beyond the structured fields; it says nothing about empty banks or result size.

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 tight sentences, with the core 'what' front-loaded before the rationale. The second sentence is slightly marketing-flavored but does carry usage context, so little is wasted.

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-param read tool with an output schema and full annotation coverage, the description supplies enough to call it correctly. The main residual gap is the undocumented subject_id semantics, which the schema does not backfill.

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?

With a single parameter at 0% schema description coverage, the description must compensate. 'Saved for a Subject' hints that subject_id selects the owning subject, but it never clarifies format (UUID) or what a missing/subject-less lookup returns, so it only partially fills the gap.

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 gives a specific verb (Read) and resource (the ordered reusable performance generations saved for a Subject), so the agent knows exactly what comes back. It implicitly contrasts with save_subject_performances (read vs. write) but never names the sibling outright.

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 second sentence contextualizes why the bank exists (looping takes to avoid regenerating performances), which implies when it is relevant. However, it never states explicitly when to call this versus list_generations, get_generation, or save_subject_performances, leaving the routing to inference.

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