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

Annotations already declare readOnlyHint, idempotentHint, and destructiveHint=false, so safety is covered. The description adds substantial behavioral context beyond that: markdown output, per-delivery-form pricing, `calculation_unit` and `offer_type` semantics, URL forwarding rules, and the fact that the server does not take bookings or enquiries.

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 front-loaded with what the tool returns and then adds operational guidance. It is somewhat lengthy and repeats the pricing-per-delivery-form concept, but every paragraph carries useful context for an agent handling prices and URLs.

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 structure does not need to be fully described, yet the description still provides crucial operational context about price presentation and URL handling. Combined with the 100%-documented `guid` parameter and read-only annotations, an agent has everything needed to call and interpret 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% and the single `guid` parameter is documented with an example in the schema. The description adds no additional meaning about the identifier itself, so the baseline of 3 is appropriate for a high-coverage 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?

The description opens with a specific verb and resource — "Returns one seminar with its description, agenda and prerequisites" — and explicitly distinguishes it from `seminars_search`, which "carries the amounts alone." An agent can tell this is the detail-fetch tool for a single seminar.

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 clear context for use (retrieving one seminar's full details) and routes users away from this server for enquiries or bookings. It also names `seminars_search` as the amount-only alternative and provides a fallback when the URL field is missing, but it does not explicitly say when to prefer this over sibling facet tools like `seminar_dates`.

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