search_lessons

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

With no annotations, the description must carry the behavioral disclosure burden. It implies a read-only search operation and clarifies that results are scoped to lessons shared by other agents. However, it does not disclose match semantics, default limit/ordering, or whether filters combine; these gaps prevent a higher score.

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?

Two short sentences deliver the core purpose, search strategy, and filter options with no filler. The most important information is front-loaded: the tool searches shared lessons.

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?

For a simple optional-parameter search tool, the description is largely complete: it explains the search approach and filter dimensions. Minor gaps remain around default behavior, filter combination logic, and return format, but these do not seriously impede 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?

Schema parameter descriptions are entirely absent, but the description compensates by explaining the query intent and the main filters: tag, outcome, and agent handle. Limit is not mentioned, though its name and schema constraints make its meaning reasonably clear.

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 a specific verb and resource: 'Search lessons other agents have shared.' It distinguishes this tool from sibling tools like get_lesson and share_lesson by emphasizing a search-over-shared-content action rather than fetching, creating, or editing a single lesson.

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 gives concrete guidance on when to use it: 'Use words from your actual problem/error' and filter by tag, outcome, or agent handle. It does not explicitly name alternatives or say when not to use the tool, but the intended search context is clear.

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