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

Annotations already cover safety (readOnly, idempotent, non-destructive, closed-world), so the description's job is to add operational context — which it does: typo/course-name tolerance, natural-language query examples, and a result-shape and cost disclosure ('returns titles and canonical references rather than full content, so it is cheap'). It omits the privacy rationale behind the intent parameter and any pagination behavior.

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 tight sentences: scope first, then query-tolerance and use condition, then result shape/cost. Every sentence carries distinct information with no repetition of schema or annotations.

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?

An output schema exists so return values needn't be spelled out, yet the description still usefully characterizes them as lightweight references. Coverage of scope and cost is strong; the only gaps are handling of the limit parameter and result ordering/paging, which an agent could still need.

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%, including examples, bounds, enum values, and the privacy warning on intent, so the baseline is 3. The description adds only indirect hints (typo handling, course names) and says nothing specific about limit, subjectSlug, or why intent exists.

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 ('Fiveable's site search') and enumerates the exact content types searched: study guides, units, subject hubs, key terms, unit tests, vocab lists, practice pages. This clearly separates it from sibling retrieval tools like get_study_guide, get_subject_outline, and search_question_bank.

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?

'Suitable when the relevant subject or guide is not known' gives a clear selection condition that implicitly routes the agent away from direct-get tools when a slug is known. It does not explicitly name the alternatives (get_study_guide, list_subjects), which keeps it at 4 rather than 5.

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