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

Annotations already declare readOnlyHint=true, destructiveHint=false, and openWorldHint=false, so safety is covered. The description adds domain context that the piece is ECharts-based, user-editable, and exports to PowerPoint as a native chart or table. It still does not say what the call actually returns (a spec, a template, instructions), which is the key behavioral question for a guide 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?

It is a single sentence with no wasted preamble, but the colon construction is muddled: the clause after the colon describes the end user's workflow rather than the tool's behavior. The core information is not cleanly front-loaded.

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 read-only guide tool with no output schema, the description must explain what the caller receives and how to apply it. It never states the return shape or that the result is meant to inform a subsequent deck_write_slide call, leaving a meaningful gap for a two-parameter, guide-style tool.

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 both document_id and type are documented in the schema, and the enum values are listed. The description adds nothing about how type changes the returned format beyond restating that charts and tables exist. Baseline 3 applies when the schema carries the parameter documentation.

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 is a noun phrase describing the subject matter ("The format of a Deckly chart (ECharts) or table") rather than stating what the tool does. The name and title say "guide", but the text never says it returns a format specification or instructions. An agent must infer the action from the name alone.

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?

No when-to-use guidance is given, and no sibling is referenced. With related tools like design_guide, deck_write_slide, and deck_edit_slide present, an agent gets no signal about when to call this guide versus writing a slide directly. The PowerPoint export note hints at intent but is not a usage instruction.

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