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

Annotations cover the safety profile (readOnlyHint=false, destructiveHint=false, openWorldHint=false), and the description adds real behavioral detail beyond them: defaults to title-body/title layouts, unfilled layout areas remain as visible user prompts, and the board-citation convention. It does not say whether reusing an existing deck name overwrites or errors, which is a meaningful omission for a write 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?

Long, but front-loaded with purpose and the doc-vs-deck fork, then rules, then a worked example. The example and layout list justify their length given the non-obvious dialect, though the rules block is dense enough that a reader must parse carefully.

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?

There is no output schema, yet the description closes the loop by telling the agent how to surface the created deck ([[board:ID]]), and the required/optional parameter split is clear. Nothing essential for a correct call 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?

Schema coverage is 100%, so the baseline is 3, but the description goes further by fully specifying the outline's mini-language (slide delimiters, layout options, area splitting, bullet handling) that the schema only gestures at as 'the markdown outline (dialect above)'. It adds genuine meaning over the structured fields.

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 verb and resource ('creates a deck from a markdown outline') and immediately distinguishes itself from siblings: it is the writing counterpart to napkin_deck_outline and explicitly not napkin_docs_create. An agent can route correctly without opening any 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 and when-NOT-to-use guidance: decks vs prose documents ('write this up' → napkin_docs_create), and states that the outline dialect matches the reader tool. It even specifies the post-write step of citing the deck with [[board:ID] on its own line.

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