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

Annotations already declare readOnlyHint=false and destructiveHint=false, so the agent knows this is a write operation that isn't destructive. The description adds no further behavioral context—it does not mention whether repeated calls create duplicates (idempotentHint=false), how existing templates are handled, or any side effects. With the bar lowered by annotations, the description still fails to add value beyond stating the purpose.

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 short sentence, which is concise, but it is under-specified—it does not front-load key details like the required HTML content or the fact that this creates a reusable template. It is not verbose, but it lacks the informational weight needed to be effective. The sentence is not a tautology, so it earns a midpoint score.

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 creation tool with three parameters and an output schema, the description is too minimal. It does not explain the expected workflow (e.g., that the template can be used with fill_template later), nor does it clarify the output format despite the output schema existing. It also fails to differentiate from sibling tools like save_deck or generate_deck. The description leaves the agent guessing about side effects and usage flow.

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 100%, so the schema already documents all three parameters (name, description, html_content). The description does not add any parameter-level detail, such as the role of {{variables}} in html_content or how name uniqueness is enforced. Per the baseline rule, 3 is appropriate since the schema does the heavy lifting.

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 uses the verb 'design' with a resource of 'new document layout', which clearly implies creating a template. It distinguishes from siblings like list_templates and preview_template by focusing on creation. However, it could be more explicit by saying 'Create' rather than 'Design', and it doesn't mention that the layout is stored as a reusable template.

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 provides no guidance on when to use this tool versus alternatives such as preview_template or fill_template. It does not mention prerequisites, like having HTML content prepared, or that it should be used before fill_template. No exclusions or alternative references are given.

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