render_template

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

With no annotations, the description carries the full burden. It discloses that the tool returns HTML/layers or a placeholders list if required content is missing, which is useful. However, it does not mention whether the operation is read-only, if it has side effects, or any auth/rate-limit requirements. The output conditionality adds some transparency but not enough for a mutation-like tool (rendering implies creating something).

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 two sentences, front-loads the primary function, and avoids unnecessary words. It conveys the core behavior, inputs, and conditional output efficiently without 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?

Given the tool has 3 parameters, a nested object, and no output schema, the description is incomplete. It does not explain what 'Paper' is, the format of the returned HTML/layers, the structure of placeholders, error conditions, or how content_overrides interact with required brand fields. An agent would need more detail to call this tool correctly in ambiguous situations.

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 description coverage is 0%, so the description must compensate. It lists the brand tokens (name, primary, background, accent, secondary, font, handle, tagline) and mentions template_name and content_overrides implicitly. This adds meaning beyond the bare schema, but it does not explain the expected format (e.g., hex codes for colors, structure of content_overrides) or the purpose of each token.

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 renders a brand design template into Paper MCP script or JSON layer spec, with a specific verb and resource. It mentions the inputs (template name, brand tokens, content overrides) and outputs (HTML/layers or placeholders). It doesn't explicitly differentiate from siblings like generate_creatives, but the purpose is distinct enough.

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 does not provide any guidance on when to use this tool versus alternatives, nor does it state any exclusions or prerequisites. It simply says what it does. With many sibling tools that might also generate design content, this is a significant gap.

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