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

Annotations only give the generic safety profile (readOnly false, non-idempotent, non-destructive); the description adds materially: the call is asynchronous and takes 20-40 minutes, the user must open the returned link and confirm before generation runs, and they are notified on completion. It also imposes a fidelity constraint on the summary (don't fabricate). It stops short of covering permissions, rate limits, or whether repeated calls duplicate work.

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 trigger condition and the call-to-action (return link, state the 20-40 minute wait) are front-loaded and useful. The English sentence largely restates the Chinese, which is redundant but brief and keeps the definition usable for an English-reading agent.

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 9-parameter creation tool with no output schema, the description covers the essential loop: when to call it, how to fill the fields faithfully, what comes back (a link), and what the user should be told. It omits nothing an agent needs to invoke it correctly, though detail on the returned artifact's life-cycle would make it exhaustive.

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 goes further by explaining the intent behind specific fields - confusions is what will be explained in depth, understood is what the learner already grasps, and the whole summary must be faithful to the conversation rather than invented. That adds real guidance beyond the schema labels.

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 action (hand the finished discussion to Bloom) and a concrete artifact (an illustrated study guide with images, diagrams and chapter-by-chapter explanations). It also distinguishes itself from the sibling search_bloom by being the create/generate side of the pair.

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?

Explicitly names the trigger conditions: the user has finished discussing a topic, learned something, or asked to systematically organize/review/go deeper. It also prescribes the post-call flow (return the link, tell the user it takes 20-40 minutes). It does not name an alternative tool or a when-not-to-use case, so it falls short of a 5.

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