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

Annotations already declare readOnlyHint=true and openWorldHint=false, so the safety profile is covered. The description adds genuinely useful non-annotation behavior: hidden courses are included, no page URLs are returned, and it spells out the paging mechanic (raise offset by limit until a page holds fewer than limit). Minor gap: no explicit note on auth or rate limits.

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?

Front-loaded with the core scope and the sibling routing, with the return envelope and paging instructions following. It is dense and packs a lot into a few sentences, though the long return-field list is the least essential clause.

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?

No output schema exists, and the description compensates by enumerating the returned fields (id, name, slug, catalog flags, subjects, enrollmentCount semantics) plus pagination strategy. Nothing an agent needs to call this correctly is missing.

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 100%, so the baseline is 3. The description goes beyond the schema by giving a concrete paging algorithm tying limit and offset together, which adds operational meaning neither parameter documents alone.

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 (list every course on the site) and pins the scope as the full inventory including hidden courses and slug-less records. It explicitly distinguishes itself from `search` and `course_get`, so an agent can route without opening any 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?

Explicitly names the alternatives and the condition that selects each: use `search` for keyword lookups plus public page URLs, `course_get` for a single course's record. It also states the negative case (no keyword filter) that would otherwise tempt a wrong call.

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