subscription_templates_reorder

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. The description adds nothing beyond that: it does not disclose whether omitted templates are left untouched, whether positions are renumbered globally, or what happens on partial input.

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?

Three words, front-loaded and free of waste, but the brevity is under-specification rather than discipline. It is appropriately scoped as a one-liner but fails to earn its space with any operational detail.

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 output schema, 0% schema description coverage on a nested-array payload, and no annotations detail, the description leaves the agent without enough to construct a correct call. A sentence on payload shape and ordering semantics is needed.

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 0% and the description does not compensate. The single 'items' parameter is a nested array of uuid/viewPosition pairs whose meaning (absolute vs relative position, required completeness of the list) is left entirely unexplained by both schema and description.

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 ('Reorder') and resource ('subscription templates'), so the operation is unambiguous. It does not, however, differentiate itself from the many other *_reorder siblings (nodes_reorder, hosts_reorder, squads_reorder, sub_page_configs_reorder) beyond the resource noun, and gives no hint at what ordering means here.

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 when-to-use guidance, no prerequisite (e.g. that existing templates must be known), and no mention of alternatives. The agent must infer everything about invocation context from the name alone.

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