Create a post template

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

Annotations already communicate that this is a non-read-only, non-destructive, idempotent write operation, so the description does not need to restate that. It adds one useful behavioral detail: the body supports embeds and a paywall marker. It does not disclose overwrite behavior or naming semantics, but those are not required given the annotation coverage.

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 with no filler. The first sentence front-loads the action, and the second adds a single concrete body-format detail without duplicating schema information.

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 simple creation tool with full schema coverage and informative annotations, the description is nearly complete. It covers what the tool does, the body format, and how the body relates to create_draft. The only minor omission is explicit mention of the return value or overwrite behavior, but these are not critical for an agent to invoke the tool correctly.

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?

All three parameters have schema descriptions, so the baseline is 3. The description adds meaningful guidance by clarifying that the body accepts the same markdown as create_draft, including embeds and a paywall marker, which goes beyond the schema's generic 'markdown or HTML' note.

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 states 'Save a reusable post template,' a specific verb plus resource that clearly communicates the tool's purpose. It references create_draft for body format, which adds useful precision, but it does not explicitly distinguish this from the related create_draft_from_template sibling.

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 implies the primary use case—saving a reusable template—and gives a concrete hint that the body follows create_draft's markdown format. However, it does not explicitly state when to choose this tool over create_draft or create_draft_from_template, nor does it mention any exclusions or prerequisites.

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