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

Annotations already establish the read-only, idempotent, closed-world safety profile, so the description's burden is lower. It still adds real value by disclosing the 'published' filter constraint and enumerating the returned fields (title, description, discipline, level, duration, objectives, link), which is the only signal about the shape of the response since no output schema exists.

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?

A single front-loaded sentence: verb, resource, scope, then the field list. Nothing is padded, and the trailing enumeration earns its place by standing in for the absent output schema.

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?

For a zero-parameter read tool with annotations covering safety and no output schema, the description supplies the needed remainder: the filter semantics ('published') and the return fields. It stops short of noting pagination or ordering, which is a minor gap for a catalogue 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, which is the baseline-4 case. The description correctly signals that the call needs no input, consistent with the empty schema.

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 (published mentor.energy courses), plus the scope and audience (energy professionals: oil & gas, geoscience, engineering). An agent can immediately distinguish this from get_course_outline and get_lesson, which retrieve a single item rather than the collection.

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?

The word 'published' implies this returns the catalogue rather than drafts or a specific course, which is enough for an agent to pick it over get_course_outline. However, it never explicitly names an alternative or states when not to use it, so usage is only implied.

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