Render deck

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

Without annotations, the description carries the burden of behavioral disclosure. It reveals that 'pdf' returns a structured not-available error, which is helpful. However, it does not clarify whether the operation is read-only or modifies state, or any permissions required, so significant transparency is lacking.

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 sentence that is dense with information: it states the action, the resource, the optional theme, and the format limitation. Every word earns its place.

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?

The description covers the main functionality and the pdf edge case, but it lacks explanation of what 'IR' stands for, what the output looks like, or any potential side effects. This is a moderately complex tool with 3 parameters and no output schema, so more detail would be useful.

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 coverage is 0%, so the description must compensate. It adds meaning for 'format' by noting pdf is Phase 3, and 'themeId' via 'optionally with a new theme'. However, 'deckId' is not explicitly explained beyond the word 'deck', leaving some ambiguity.

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 verb 'Re-render' and the resource 'stored deck from its IR', with an optional theme. It distinguishes from sibling tools like generate_deck by implying a re-rendering operation on an existing deck.

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 description gives clear context that this is for re-rendering an existing deck and notes the pdf format is a Phase 3 limitation. However, it does not explicitly state when to use this vs. alternatives like generate_deck, or provide when-not-to-use guidance beyond the pdf caveat.

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