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

Annotations already declare readOnlyHint=true, openWorldHint=false and destructiveHint=false, so safety is covered without the description. The text adds that the content includes the checks the code performs and the quality bar, which is useful context about what comes back, but says nothing about whether it is static or versioned.

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?

A single compact sentence with no filler, and the applicable work types are front-loaded. The nested quoting around 'deck', 'landing' and 'ad' is slightly awkward but costs nothing.

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?

This is a simple one-parameter read tool with an output schema, so return values need not be explained. The description covers content, the three applicable work types, and the tool's read-only nature; only its position in the workflow (before starting work) is left implicit.

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 schema has one undocumented string parameter at 0% coverage with no enum, so the description carries the burden — and it does name the three concrete values ('deck', 'landing', 'ad') an agent should pass. That is meaningful compensation for the schema gap, though it doesn't state whether other values are accepted.

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?

Describes the content of the resource (code checks, quality bar, process) rather than stating the verb — it never says it returns a design brief document. An agent can infer it is a reference lookup, but the purpose is stated obliquely and is not distinguished from the sibling deck_piece_guide.

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 scoping phrase 'for "deck", "landing" or "ad"' implies this applies to those three work types, which is weak usage guidance. There is no explicit 'call this before writing a slide/page' instruction and no mention of how it differs from deck_piece_guide, which appears to be a comparable guide tool.

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