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

Annotations already declare readOnly, idempotent, non-destructive, and closed-world, so the safety profile is covered. The description adds real behavioral value by disclosing the shape of what comes back (ordered pathways, planned-but-unreleased pathways included, per-module fields) and that no parameters are needed. It does not mention volume or pagination, which is the only remaining gap.

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 dense sentence that front-loads the resource and then the payload, with the usage clause and sibling handoff appended. No filler, no restatement of the title, and the parenthetical field list is compact rather than a bulleted dump.

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?

There is no output schema, so the description carries the burden of describing return content — and it does so concretely, down to individual module fields and the inclusion of planned pathways. Combined with annotations covering safety and a zero-parameter schema, nothing an agent needs in order 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?

The tool takes zero parameters, so the baseline is 4; there is nothing for the description to disambiguate. It correctly implies the call is argument-free by framing the tool as a whole-catalog dump rather than a filtered lookup.

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 (the Slop Curriculum on learn.slopped.site), then enumerates exactly what the listing contains: ordered pathways including planned ones, per-pathway modules with number/id/title/summary/link, and badge-certified abilities. This is clearly distinguishable from get_module, which is named as the drill-down counterpart.

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?

Gives two concrete use cases ('recommend what to learn next' and 'find a module id for get_module') and explicitly routes the agent to the sibling get_module for the follow-up step. An agent knows both when to reach for this tool and what to do after it returns.

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