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

Annotations already carry readOnlyHint=true, idempotentHint=true, and destructiveHint=false, so the safety profile is covered. The description adds genuine behavioral value on top: the list is complete, needs no pagination, and takes no arguments — useful facts not derivable from the annotations or schema. No contradiction with annotations.

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?

Three tightly packed sentences, front-loaded with purpose before return format and invocation notes. Every sentence earns its place; there is zero filler or redundancy.

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 a zero-parameter surface, an existing output schema, and complete annotations, the description covers everything an agent needs: what it returns, where from, and that no pagination or arguments are required. Nothing is missing for correct invocation.

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 and schema coverage at 100% (empty schema), the baseline is 4. The description appropriately states 'No arguments' and explains why (complete list, no pagination), which fully removes any doubt about invocation. Nothing more could be demanded here.

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/list) and resource (free courses at alexandrecaramaschi.com/educacao) and is clearly distinguishable from siblings like getCourseDetails, which fetches a single course by slug. The return payload is spelled out (hub URL, course count, per-course slug/title/track/level/canonical URL), leaving no ambiguity about what this tool is for.

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?

Offers clear when-to-use guidance: deploy this tool 'before asking for one by slug,' which establishes the discovery-then-fetch flow relative to getCourseDetails/getCourseModules. It does not explicitly name the alternative tool or state exclusions, but the contextual cue is sufficient for an agent to route correctly.

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