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

Annotations already declare readOnlyHint, idempotentHint, non-destructive and closed-world, so the safety profile is covered. The description's added value is disclosing what the payload contains (layouts, per-field limits, targets, film-only scenes, payload_atoms), which matters since no output schema exists, but it never clarifies what 'targets' or 'film-only scenes' actually are.

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?

One front-loaded sentence that starts with the action and ends with the usage instruction, with no filler. It is dense and runs long on parenthetical enumerations, but every clause carries information.

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 and no parameters, the description must convey the return shape, and it does so at a high level (layouts, field limits, targets, film-only scenes, payload_atoms). The unexplained terms are a modest gap but not a blocker for an agent deciding to call it.

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?

The tool takes zero parameters and the schema is an empty object, so there is nothing to disambiguate; the description correctly implies a single no-argument call. Baseline 4 applies for a parameterless tool.

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?

Opens with a specific verb+resource ('List the slide layouts the PPTX renderer builds') and enumerates the layout types, so an agent knows this is a schema/introspection call rather than a rendering call. Some listed payload items ('the targets', 'the film-only scenes') are named without explanation, which blurs what exactly is returned.

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?

'Read this before writing a deck' gives an explicit trigger condition that positions it ahead of deck_build/deck_validate. It does not name those siblings or state when-not to call it, but the sequencing guidance is unambiguous.

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