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

Annotations already cover the safety profile (readOnly, idempotent, non-destructive, not open-world), yet the description adds genuinely new behavior: a curated set when available, otherwise slower generated questions. This fallback/slowness detail is real added value beyond the annotations, though it omits latency or determinism implications for the generated path.

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 no filler, front-loaded on what is returned and the fallback condition. The intended-use clause is slightly appendage-like but still earns its place by signaling purpose.

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?

Output schema exists so return values need not be explained, and the description covers the key behavioral nuance (curated vs generated). For a one-parameter read tool this is largely complete, with only minor gaps around how the fallback affects speed or result shape.

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 100% schema description coverage and a single required guideId, the schema already documents the parameter fully. The description only repeats 'Accepts a guide id' without adding format, valid ranges, or sourcing constraints, so 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 verb and resource ('Returns reading-check questions and keys for one Fiveable guide') and clarifies the scope is a single guide. It does not explicitly differentiate itself from siblings like get_questions_for_materials or get_study_guide, but the resource is narrow enough that an agent can distinguish 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?

It names intended uses ('exit tickets, reading quizzes and guided reading handouts'), which implies when to reach for it, but gives no exclusions or explicit alternatives to compare against, such as get_questions_for_materials. Usage is implied rather than guided.

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