Create a post template

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

Annotations already declare this as a non-read-only, non-destructive, non-idempotent, open-world write. The description adds genuinely useful content-layer behavior: the body accepts the same markdown as create_draft, including embeds and a paywall marker. It is silent on permissions, duplicate-name behavior, and whether the template is scoped to a publication, so the added value is moderate.

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 tight sentences with no filler, front-loading the action and resource before the body-format detail. Every clause carries 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 write tool with full schema coverage and annotations, the description is nearly adequate, but with no output schema it never says what is returned (e.g., a template id) and gives no guidance on duplicate names or publication scoping. Those omissions matter for correctly chaining into create_draft_from_template.

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 100%, so the baseline is 3. The description goes beyond the schema by telling the agent that 'body' follows create_draft's markdown conventions including embeds and a paywall marker — semantic constraints the schema's generic 'markdown or HTML' text does not convey.

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?

States a specific verb and resource: 'Save a reusable post template.' The adjective 'reusable' distinguishes it from create_draft (creates a post), and the cross-reference to create_draft's body format reinforces the boundary. It does not explicitly contrast with siblings like create_draft_from_template, so it stops short of a 5.

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?

There is no when-to-use or when-not-to-use guidance, and no alternative is named. The only contextual hint is that the body format matches create_draft, which implies a relationship but does not tell the agent when to save a template rather than a draft.

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