Save a caption template

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

Annotations already declare this a non-read-only, non-open-world write, so the safety baseline is covered. The description adds genuinely useful behavior beyond that: the operation is an upsert ('creates or replaces') and `extends` performs a merge with appended guidance. It omits what happens to the existing template on replace (irreversibility) and any auth or quota context.

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, front-loaded with the core action and then the one non-obvious parameter's semantics. No filler or repetition of the title.

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?

With 13 parameters, 0% schema description coverage and no output schema, the description is far too thin for the tool's complexity. An agent can infer the overall effect but cannot confidently populate most fields or anticipate the overwrite consequence of reusing an existing name.

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% across 13 parameters, so the description must carry the burden and it does not. It explains only `extends` and, partially, the merge behavior of hashtags, mentions, collaborators and guidance; the other parameters (name pattern, hashtags_in enum, location_id, caption_header/footer, first_comment, is_ai_generated) get no meaning at all.

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 opens with a specific verb-plus-resource statement, 'Creates or replaces a caption template,' which immediately tells the agent it is an upsert on a named template. It is clearly distinct from siblings like list_templates and delete_template, though it does not explicitly name them.

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?

It gives one concrete usage rule: use `extends` to build on another template. It does not say when to prefer this over generate_caption or when not to call it, nor does it warn that saving under an existing name overwrites the prior template.

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