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

Annotations already declare readOnlyHint=false, destructiveHint=true, idempotentHint=false, so the mutation profile is covered. The description usefully adds that the call returns seliee_template_id and seliee_template_uuid, but it never explains why a 'create' is flagged destructive (e.g., overwriting an existing seliee_template for that base) — that is the one behavior an agent most needs before calling.

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, zero filler, with the action and its seeding source front-loaded before the return values. 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?

With no output schema, the description compensates by naming the returned IDs, which is good. But for a destructive, non-idempotent, openWorld=false mutation with two optional-and-ambiguous identifier params, the missing pieces — overwrite behavior and what to do when both params are null — leave the definition only partially sufficient.

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% and neither parameter has a description, so the description carries the burden. It names both parameters and the 'or' phrasing hints that either identifier form is acceptable, which is real added meaning. However, it does not resolve the ambiguity that both params are nullable and required-count is 0 — it says nothing about what happens if neither or both are supplied.

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 gives a specific verb and resource ('Create a new seliee_template') plus the key qualifier 'seeded from a base templates document', which distinguishes it from plain create_template or create_publish_website_template in the sibling list. It does not name a sibling outright, 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?

Usage is only implied: an agent can infer this is the tool for duplicating an existing base template rather than authoring a blank one. There is no explicit statement of when to pick this over create_template, no prerequisites (does the base template need to exist / be visible?), and no failure conditions.

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