Retrieve Lessons

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

Annotations already declare readOnlyHint=true, so the description's 'Retrieve' aligns with a safe read operation. The description adds value by specifying the usage context (PreToolUse hooks), but does not disclose additional behaviors like rate limits or empty result handling.

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 extremely concise with two sentences, front-loading the purpose. Every word serves a function with no redundancy or filler.

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 the simple retrieval operation, high schema coverage, and annotations covering safety, the description is mostly complete. It could mention return format or behavior on empty results, but overall it provides sufficient context for an agent to use the tool correctly.

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?

Schema description coverage is 100%, so the description does not need to compensate. The description hints at relevance ranking ('most relevant'), adding slight context beyond the schema, but not enough to raise the score above the baseline of 3.

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 the most relevant lessons for a given tool/action context, specifying both the action and the resource. It distinguishes itself from sibling tools like search_lessons by focusing on per-action guidance in PreToolUse hooks.

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 explicitly says to use this tool in PreToolUse hooks for per-action guidance, providing clear context. However, it does not mention when not to use it or list alternatives like search_lessons, which could help differentiate.

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