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

Annotations mark it non-destructive but also readOnlyHint=false, implying generation of new content, yet the description adds nothing beyond that: no indication of whether the output is text, markdown, a file, or a link, how many slides, or what the generated content covers. 'RETURNS: PPT 内容' is too vague to carry the burden for a no-output-schema generation tool.

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 pipe-delimited block is short and front-loads the purpose, trigger, aliases, and return in a scannable order. Minor redundancy between the name, title, and aliases, but no wasted prose.

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 single-parameter generator with no output schema, the trigger side is complete, but the output side is not: an agent cannot tell what shape the returned PPT content takes or how to present it to the user. That gap keeps it at minimum-viable rather than complete.

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 only one parameter (topic) and schema description coverage is 100%, so the schema already defines it as 研究主题. The description does not add constraints such as topic granularity, language, or scope, so 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?

The description names a specific verb+resource: producing slide/presentation content for a research topic, reinforced by the Chinese title 选题汇报 PPT. An agent can distinguish it from outline-oriented siblings like paper_outline or literature_review_outline by the 'PPT / slide content' framing, though it never explicitly contrasts with them.

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?

The 'USE WHEN' clause gives a concrete trigger: the user wants slide content or presentation material for a topic, with examples (开题汇报 / 组会汇报) and alias keywords that help intent matching. It stops short of stating when NOT to use it or naming an alternative for text-only outlines.

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