subscription_templates_create

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

Annotations already declare readOnlyHint=false and destructiveHint=false, so the safety profile is covered structurally. The description adds nothing: no statement of required permissions, whether the name must be unique, what defaults apply to an unconfigured template, or what the call returns. For a creation tool it is essentially a restatement of the name.

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?

A single front-loaded fragment with zero padding, so there is no waste to cut. However, brevity here is under-specification rather than economy: at four words it cannot carry the two undocumented parameters or the mutation's side effects.

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?

A mutating tool with two required parameters at 0% description coverage, no output schema, and a large sibling set that needs disambiguation. The definition leaves the agent to guess at template-type semantics and post-creation steps without any compensating text.

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 0% and the description documents neither parameter. The agent gets no meaning for 'name' (uniqueness, name-vs-display-name, the regex/max-length intent) or for 'templateType' (what XRAY_JSON vs CLASH vs SINGBOX mean for downstream rendering). Structured schema gives valid syntax only, not semantics.

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 clear verb+resource pair ('Create subscription template') that an agent can act on immediately. It does not distinguish itself from siblings like subscription_templates_update, subscription_templates_reorder, or sub_page_configs_create, all of which are adjacent operations in the same family.

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?

No guidance on when to create a template versus updating or reordering one, no prerequisites, no mention of tag/link steps (subscription_templates_set_tags) that typically follow creation. The agent must infer the workflow entirely from the name.

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