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

Annotations already declare read-only, idempotent, non-destructive, open-world behavior, so the bar is lower. The description still adds real substance beyond them: alias matching ("K8s" → "Kubernetes") and the crucial semantic that a hit proves vocabulary existence, not seminar existence. It omits that the same lookup spans non-topic vocabularies (manufacturer, audience, software_version), which is a noticeable blind spot.

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 tight paragraphs: purpose first, usage second, the disambiguating caveat last. Every sentence carries information — the alias examples and the filter-axis-versus-catalogue distinction both do real work.

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?

An output schema exists so return values need no explanation, and the annotations cover the safety profile. What an agent needs to call it correctly is essentially present; the only gap is that the `type` parameter's broader vocabularies are never mentioned, which slightly undercuts the 'topic vocabulary' framing.

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 baseline is 3. The description earns a point above that by documenting matching semantics the schema does not: the `query` value is matched against aliases as well as names, and the result is meant to be reused as a filter value. It says nothing about the `type` facet values, leaving that entirely to the schema.

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?

Opens with a specific verb+resource: searches the topic vocabulary seminars are tagged with. It immediately frames the tool as a lookup that feeds `seminars_search`, which distinguishes it from that sibling without the agent needing to open either schema.

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?

Gives explicit when-to-use (turn a customer's wording into a filter value, check whether a product/technology is covered) and an explicit when-not ("a hit means the topic exists, not that a seminar on it does. `seminars_search` answers that"). The alternative is named and the condition that selects it is stated.

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