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 genuinely new behavioral context: the return payload is raw HTML, the cost model is FREE (no AI, no credits), and the caller is instructed to render the result as an artifact. It stops short of covering error cases (invalid session_id) or very large sessions.

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 purpose and the artifact-rendering directive before the routing guidance and cost note. The dash-delimited list of generate_document use cases is slightly long but each item earns its place by sharpening the sibling boundary.

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 return-value burden and does so: it enumerates the contents of the HTML (logo, brand colours, agenda table, activity cards) and tells the agent what to do with it. For a one-parameter read tool with full annotations, nothing an agent needs is missing.

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?

There is a single parameter with 100% schema description coverage ('The Metodic session (toolkit) id.'), so the schema already carries the meaning. The description adds no format or sourcing guidance for session_id, so the baseline 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?

States a precise verb (return) and a precisely characterized resource: a self-contained, Metodic-branded HTML one-pager containing logo, brand colours, agenda table and activity cards. It explicitly distinguishes itself from the similarly-named generate_document, so an agent can route correctly without opening 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 ('FULL session overview: the agenda with activity detail, for the facilitator or for stakeholders who want to see the whole design') and an explicit when-to-use-the-other-tool rule naming the sibling generate_document plus the conditions that select it (participant pre-read, briefing attachment, client brief, prep notes). Nothing is left to inference.

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