subscription_template_create_template

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

Annotations are absent, so the description carries the full burden. It only restates the REST endpoint and controller, giving no information about auth requirements, the effect of creating a template, or the preview/confirm behavior (which is documented only in the schema, not the description).

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?

Very short and front-loaded with the action, but includes noise ('Tags: Subscription Template Controller') that adds no value, and the raw POST path is a restatement rather than useful framing.

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 mutation tool with a nested object body, no annotations, and no output schema, the definition is inadequate. It neither documents the required nested fields nor the confirm-gated preview behavior, leaving the agent with little to act on.

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 50% and the description adds zero parameter meaning. The nested body (name, templateType) is undocumented beyond structural constraints, and only 'confirm' has a schema description. The description does not compensate for the gap.

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+resource: 'Create subscription template'. The endpoint dump and controller tag reinforce what it does, but there is no explicit differentiation from siblings like subscription_template_update_template, though the verb makes the distinction largely obvious.

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 use this versus update/delete/get template siblings, no prerequisites, no mention of required fields or context. The agent must infer usage 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.