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

Annotations already cover read-only/idempotent/non-destructive, so the description wisely spends its words elsewhere: it discloses the account-authorization requirement on the public endpoint, that the gap subtotal excludes extra interview/placement fees, that missing selections stay explicit rather than being filled in, and that output is English natural-language text. That is meaningful context beyond structured fields, though it says nothing about result size or rate behavior for a potentially large payload.

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?

Five sentences, front-loaded with the resource and access method, then caveats, then the authorization-flagged parameter, then return characteristics. Dense but every sentence carries a distinct constraint. Minor cost is that the fee-exclusion and identity-prohibition notes are packed tightly enough to need a second read.

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 does the work of characterizing the return: English natural-language text preserving sources, conditions and pagination, plus flag-dependent fields for school identity. Given eight parameters including a conditional quote mode, it covers the essentials; a note on what happens when pathway conflicts with gapUnits/providerPublicId would close the remaining gap.

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 coverage is 63%, with the most consequential parameters (slug, locale, gapUnits, residency, includeProviderIdentity) already documented in-schema. The description adds real value on includeProviderIdentity's cost (account authorization) and on how optional selections interact to form an indicative quote, but it leaves pathway, onlineTierId and providerPublicId relationships largely to the schema. Adequate rather than compensating for the coverage 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?

States a specific verb and resource — reads qualification requirements, risks, sources, providers and RPL/gap/online prices — scoped to an exact slug. That 'by exact slug' scope cleanly separates it from the sibling search_rpl_qualifications, which is a discovery tool. An agent can tell what it retrieves without opening the schema.

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?

Gives concrete conditions: includeProviderIdentity=true when the user asks which school issues the qualification or which RTO supplies a quote, and a clear prohibition against inferring hidden identities or treating a candidate as approved. It does not explicitly say to run search_rpl_qualifications first — that routing lives only in the slug parameter's schema description — so the guidance is strong but not complete.

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