subscription_template_update_template

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

Annotations are absent, so the description carries full behavioral burden, yet it discloses nothing beyond the HTTP verb and path. It does not mention that this is a mutation, what gets overwritten, or permission/confirmation requirements (the confirm preview behavior is only described in the schema).

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 operation, which is good, but the trailing 'Tags: Subscription Template Controller' line is boilerplate noise that adds no selection value.

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 no annotations, no output schema, and only half the parameters described, the description is too thin. It omits confirmation semantics, permissions, and the effect of the update, leaving the agent under-informed.

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 50% and the description adds no parameter meaning at all. The nested body fields (name, uuid, templateJson, encodedTemplateYaml) are undocumented in prose, so the description fails to compensate for the coverage 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 and resource ('Update subscription template') plus the underlying endpoint (PATCH /api/subscription-templates), so an agent knows it mutates an existing template. It does not distinguish itself from siblings like subscription_template_create_template or subscription_template_get_template_by_uuid beyond the resource name.

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 create/get/delete template siblings, nor any prerequisites such as needing an existing UUID. The only content is the operation and a controller tag.

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