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

Annotations already declare readOnly, idempotent, non-destructive and closed-world, so the safety profile is covered. The description adds real value beyond that: the corpus size ('hundreds'), that user-saved methods are included, and that it is 'free and instant' with no side effects. Return-shape specifics are implied (timing/instructions/tips/materials) rather than detailed, which is acceptable here.

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?

Front-loaded with the core action and the imperative usage rule, then filters, then a practical note. It is on the longer side for a 3-parameter search tool, but each sentence carries distinct information with no 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?

With no output schema, the description carries the burden of describing return content, and it does list what each method includes (timing, step-by-step instructions, facilitator tips, materials) plus saved user methods. An agent has enough to call it correctly; only pagination/result-count behavior is unaddressed.

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 query, category and max_duration are already documented with examples in the schema. The description's 'Filter by keyword, max duration and category' restates them without adding syntax, units or edge-case behavior, so the baseline of 3 applies.

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 states a specific verb and resource: searching a library of proven facilitation methods, with explicit scope (timing, instructions, tips, materials, plus user-saved entries). An agent can tell it apart from generation tools in the sibling list, though no sibling is named directly.

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?

It gives a strong, unambiguous when-to-use rule: 'ALWAYS use this before suggesting an activity, exercise, energiser, icebreaker, ideation format, retro or workshop segment.' It also explains the rationale (recommend tested methods rather than inventing). It does not name alternatives such as find_session_format or list_frameworks or state when not to use it.

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