subscription_template_reorder_subscription_templates

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

No annotations are provided, so the description carries the full burden. Aside from the raw HTTP verb 'POST' hinting at mutation, it discloses nothing about permissions, whether the reorder is atomic, what happens to templates omitted from the items array, or the preview behavior tied to confirm.

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?

The text is a raw OpenAPI endpoint dump: the URL path is front-loaded ahead of the actual purpose, and the 'Tags: Subscription Template Controller' line is pure noise for an agent selecting a tool. It is short but poorly structured for its audience.

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 endpoint with nested request bodies, no annotations, and no output schema, the definition is too thin: no ordering semantics, no confirmation/preview explanation, no error or permission context. An agent could invoke it but not confidently.

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 no parameter meaning at all. It does not explain the items array, how viewPosition maps to ordering, or the confirm preview behavior, leaving the description to compensate for the coverage gap and failing to do so.

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 states a specific verb and resource ('Reorder subscription templates'), which the agent can distinguish from read/write siblings by the tool name. However, it does not differentiate the effect from lookalikes such as config_profile_reorder_config_profiles, internal_squad_reorder_internal_squads, or node_plugin_reorder_node_plugins 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?

There is no guidance on when to use this reorder tool versus the other reorder siblings, nor on prerequisites (e.g., needing the full set of templates, or that viewPosition values define order). The agent is left to infer everything from the name.

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