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

Annotations already declare destructiveHint=true, so the overwrite risk is covered structurally. The description still adds genuinely new behavior: the stylesheet is replaced wholesale and every slide is re-measured afterwards, which tells the agent about layout reflow side effects. It omits what happens to fonts when they are not supplied and whether the previous stylesheet is recoverable.

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?

Two short sentences with no filler; the primary action is front-loaded and the secondary side effect (re-measuring slides) follows. Nothing in the text could be removed without losing 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 full schema coverage on four parameters, the description covers enough to invoke the tool but not enough to invoke it confidently in context: the relationship to deck_edit_styles, and what the agent should do after the slides are re-measured, are absent.

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 each parameter is already documented in detail, including the rich image_style id list. The description only adds the optionality of 'fonts', which the schema does not mark as required anyway; beyond that it adds no syntax or format meaning over the schema.

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 gives a specific verb and resource ('Writes the complete shared stylesheet') and adds the optional fonts scope, so the agent knows what the tool produces. It does not differentiate itself from the sibling deck_edit_styles or from deck_set_fonts, leaving the write-vs-edit distinction implicit.

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 word 'complete' hints that this is a full replacement rather than an incremental tweak, and '(and, if you want, the fonts)' signals that fonts are optional. However, no explicit when-to-use or when-not-to-use guidance is given, and the obvious alternative (deck_edit_styles) is never named.

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