list_transitions

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

With no annotations, the description carries the full transparency burden. It accurately conveys a simple read-only enumeration operation, with no hidden side effects or conditions to disclose. The wording 'List' inherently communicates the read-only nature, though it does not explicitly state that it returns a fixed/static set.

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?

The description is a single, compact sentence with 13 words, front-loaded with the action ('List') and the object ('reveal.js slide transition styles'). No filler or redundancy.

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?

For a zero-parameter list tool with an output schema, the description is fully complete: it names the exact set of items listed and their intended use. The output schema handles return structure, so no further detail is required.

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?

There are no parameters, so the baseline is 4. The description adds meaningful context by stating the output is 'usable as the `transition` argument,' which clarifies the purpose and relationship to other tools, exceeding the minimum for a zero-parameter 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?

The description clearly states the tool lists a specific resource: 'reveal.js slide transition styles,' and explains their usage as the `transition` argument. This verb-object-resource structure is unambiguous and distinguishes it from siblings like list_themes or list_presentations.

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 purpose makes usage self-evident: use this tool when you need the valid transition values. However, it does not explicitly present alternatives or exclusions, so it falls short of a 5, but the context is strong enough to justify a 4.

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