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

Annotations already declare this as a safe, read-only, idempotent operation. The description adds valuable behavioral context by stating there are no arguments and the list is complete and unpaged, which tells the agent not to expect pagination or filtering.

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?

The description is a tight, two-sentence block that front-loads the purpose and then details the return contents. Every sentence adds useful information with no fluff.

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?

Given that an output schema exists, the description need not explain return values in detail, yet it still summarizes the key fields. It fully covers what an agent needs to know to call this tool correctly: no arguments, complete unpaged list, and expected content.

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?

With zero parameters, the baseline is 4, but the description explicitly confirms 'No arguments', fully resolving any ambiguity about how to invoke the tool.

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?

The description states a specific verb ('discover') and resource ('free courses at alexandrecaramaschi.com/educacao and their slugs'), making the purpose unambiguous. It is clearly distinguishable from siblings like getCourseDetails or getCourseModules, which handle individual courses rather than the catalog list.

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 phrase 'list is complete, unpaged' and the context of discovering a catalog clearly imply this is the entry point before using detail tools. However, it does not explicitly name alternatives or say when not to use it, leaving some inference to the agent.

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