academy_lessons

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

With readOnlyHint: true already provided, the description adds that it returns only titles, descriptions, and duration, and that it excludes the body, which is useful behavioral context. It does not contradict annotations and adds specific information about the return content.

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 single sentence, perfectly concise, and front-loaded with the primary action and object. It also includes a necessary clarification about the body content. Zero wasted words.

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 the tool is a simple listing operation with readOnlyHint, two parameters, and no output schema, the description is quite complete. It communicates what is returned and explicitly directs to a sibling tool for more detail. Some might expect mention of pagination or ordering, but this is a minor gap for a list operation.

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 schema description coverage is 100% with clear parameter descriptions for both level (1-6) and locale (enums with defaults). The description does not add additional parameter semantics beyond the schema, so the baseline of 3 is appropriate since the schema already covers the parameter meaning.

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 clearly states the tool lists all lessons in a level with titles, descriptions, and duration, and distinguishes it from academy_lesson by noting that the full text is not included. This directly addresses the purpose and differentiates from the sibling tool that provides full text.

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 description implies when to use this tool (for a list of lessons) versus academy_lesson for full text, but it does not explicitly mention alternatives for other related tasks like searching or playbooks. The 'No body — call academy_lesson for the full text' provides a clear pointer to an alternative, but it lacks comprehensive when-not-to-use guidance for other siblings. Still, it clearly indicates context.

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