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

Annotations already declare readOnlyHint=false, destructiveHint=false, idempotentHint=false and openWorldHint=false, so the safety profile is covered. The description adds genuinely new context beyond those hints: despite being a write, saving publishes nothing. It stops short of covering auth requirements, duplicate-name behavior, or limits.

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 sentences, no filler, and the core action plus payload are front-loaded with the important non-publishing caveat last. Every clause 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?

For a create tool with full schema coverage and annotations covering the safety profile, the description is nearly complete; the "publishes nothing" note closes the main behavioral risk. It does not indicate what is returned (e.g. a template ID) despite there being no output schema, which is the only notable omission.

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 every parameter, including nested media objects and platform_settings. The description's prose list (default text, per-platform text, target accounts, settings, media, first comment) largely restates those fields; only "optional per-platform text" mildly clarifies content_overrides. Baseline 3 is correct.

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") and enumerates the payload it captures, so an agent immediately knows this creates a stored template rather than a post. It does not name a sibling, but the create-vs-update-vs-publish distinction is derivable from the name and the closing clause.

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?

Usage is only implied. "Saving publishes nothing" tells the agent this is not a publishing action and therefore differs from schedule_post, but there is no explicit when-to-use statement or exclusion relative to update_post_template or create_post_tag. Adequate but with a clear gap.

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