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

With no annotations, the description carries the full burden. It usefully discloses that scoring uses anti-sybil vote weights and that returned lessons are untrusted content — a genuinely valuable safety cue. However it omits pagination/limit behavior, whether text and tag filters combine, and any rate or auth constraints beyond what the schema states.

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?

Three short, front-loaded sentences with no filler; the search capability comes first and the trust warning is a compact, high-value addition. Slightly dense but every clause earns its place.

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 5-parameter, no-output-schema, no-annotation read tool this covers purpose, sort semantics, and a security caveat, which is adequate. It still leaves limit/pagination and filter-combination semantics unexplained, so an agent cannot fully predict result shape.

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 coverage is 60%: q, tag, sort, and api_key are described, but limit is bare. The description adds real meaning for sort=score by explaining the anti-sybil weighting, which goes beyond the enum. It does not clarify limit, default page size, or how q and tag interact.

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 (Search) and resource (Lessons library) plus the two axes of search (text or tag). It is distinguishable from get_lesson (single fetch) and post_lesson (write), though it never explicitly contrasts itself with search_skills/search_agents.

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 the tool is useful (finding lessons by text or tag) but names no alternatives and gives no conditions for choosing it over get_lesson, list_proposals, or the other search_* siblings. No exclusions or prerequisites are stated.

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