List templates, layouts and themes

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

Annotations already declare readOnlyHint=true and openWorldHint=false, so the safety profile is covered. The description adds real value beyond that: it discloses the shape of the payload (layouts include text fields and icon slots) and the intended call ordering. It doesn't describe output structure precisely, so not a 5.

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, front-loading what is enumerated and ending with the actionable directive. Every clause earns its place, including the parenthetical that preempts the question of what a layout actually contains.

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, the description carries the burden of conveying return content, and it does so at a useful level of detail (three categories plus nested layout fields). The exact response envelope and identifiers are unspecified, but for a zero-parameter catalog call this is nearly complete.

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, so there is nothing for the description to disambiguate; baseline 4 applies. No misleading parameter hints are present.

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 ("Lists") and an enumerated resource set: templates, slide layouts with their text fields and icon slots, and color themes. The parenthetical even clarifies the granularity of layout data returned. It doesn't explicitly name a contrasting sibling (e.g. get_presentation), so it falls just short of 5.

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?

"Call this first" is explicit sequencing guidance that tells the agent this is the discovery entry point before calling render_slide, add_slide, set_theme, etc. It gives clear context but doesn't name alternatives or state when not to use it, which keeps it at 4 rather than 5.

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