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

Annotations already declare readOnlyHint=true and destructiveHint=false, so the safe read-only nature is established. The description adds the 'built-in' scope and the template domains covered, but does not disclose return format, ordering, or how type/platform filtering behaves. No contradiction with annotations.

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?

One well-structured sentence with the verb and resource front-loaded. The parenthetical enumeration is long but informative and earns its place by showing exactly what template types are available.

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, read-only listing tool with zero required parameters and full schema coverage, the description is largely complete. The only minor gap is that it does not clarify the relationship to get_template or describe the output, but the annotations and schema cover the safety and parameter aspects.

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 parameters are fully documented in the schema. The description does not add parameter-level meaning, though its list of template categories partially hints at what type/platform values map to. Baseline 3 is appropriate.

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 uses a specific verb ('列出' / list) and clearly identifies the resource: built-in expert content templates, with a concrete enumeration of template types. This distinguishes it from siblings like get_template (retrieve one template) and list_categories/list_platforms (list metadata, not templates).

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 clearly frames this as a listing operation, so an agent can infer it is for discovering available templates. However, it does not explicitly say when to use this over get_template, nor does it mention filtering guidance or any exclusions.

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