list_context_lessons

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

Discloses read-only retrieval, automatic layering, and sorting, but lacks details on error behavior, caching, or side effects. With no annotations, more burden falls on the description.

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?

Concise two-sentence description plus parameter list. No extraneous information; each sentence adds value.

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?

Covers what is returned and aggregation logic, but does not explain metadata fields or compare to sibling tools. Lacks detail on output structure since no output schema exists.

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 description adds context for the directory parameter (absolute path, required), but does not explain format validation or example values. For a single parameter, this is adequate but not thorough.

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 retrieves titles and metadata of lessons matching context, distinguishing it from siblings that get context or search by tag. However, the notion of 'current context' is not precisely defined, leaving slight ambiguity.

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?

No guidance on when to use this tool versus alternatives like search_lessons_by_tag or read_lesson. The description implies it's automatic but does not specify prerequisites or exclusions.

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