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

Annotations already cover read-only/idempotent/non-destructive, so the bar is lower, and the description adds real content: presentation returns common appearance tokens plus slide guidance without other formats' adaptations, and a stated precedence hierarchy against task/source/recipe/Safe Static/sharing. The closing note that a reference records provenance, not visual fidelity is useful but somewhat cryptic.

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?

Purpose is front-loaded in the first sentence, which is good, but the third and fourth sentences are dense and jargon-heavy ('Safe Static rules', 'A reference records provenance, not visual fidelity') without clearly earning their space for a single-parameter read tool.

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?

No output schema exists, so the description carries some return-value burden, partially handled by describing presentation tokens/slide guidance and provenance semantics. Combined with strong annotations and full schema coverage, it is largely complete, though non-presentation return shapes remain unstated.

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?

With one enum param at 100% schema coverage the baseline is 3, but the description adds meaning beyond the enum: it signals that the 'presentation' value produces a different payload than the others. That is genuine semantic value tied to parameter choice.

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 ('Get') and resource ('active owner-authored appearance guidance') with the supported formats named. An agent can tell it retrieves style guidance, but it does not explicitly distinguish itself from the sibling preview_artifact_style or set_artifact_style.

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?

Usage is implied by the format list and the 'presentation returns...' note, but there is no explicit when-to-use/when-not-to-use guidance and no routing to alternatives such as preview_artifact_style. The precedence sentence ('Style never overrides...') constrains behavior but is not a selection rule.

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