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

Annotations already declare readOnlyHint=true, idempotentHint=true and destructiveHint=false, so the safety profile is covered. The description adds that courses are nationally recognised and lists returned attributes (unit code, price, duration, delivery, renewal), but the output schema already carries those fields, so added behavioral value is modest.

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-loads the core purpose in the first clause and ends with a routing instruction. The enumeration of returned fields is somewhat redundant with the output schema, slightly diluting conciseness, but overall it's efficient.

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 an output schema present, return-value detail needn't be in the description; it focuses on purpose and usage. It's complete enough for a no-arg catalog tool, though it doesn't note ordering or completeness guarantees of the listing.

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?

The tool takes zero parameters, so the baseline is 4. There are no parameter semantics to document and the description appropriately doesn't attempt to.

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 (List) and resource (nationally recognised first aid and CPR courses) with clear scope (Australia Wide First Aid). It implicitly distinguishes itself from get_course_details by being the catalog-level listing rather than a single-course lookup.

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 says to use it to turn a need like 'first aid for work' or 'childcare certificate' into a course id for the other tools, which gives a clear entry-point context. It doesn't name a when-not condition or explicitly contrast with get_course_details, but the usage context is well defined.

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