subscription_templates_reorder

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

No annotations are present, so the description carries the full burden of behavioral disclosure. It only states the action and input format, but does not disclose side effects, whether the reorder is permanent, permission requirements, or constraints (e.g., full list vs. partial). For a mutation tool, this is a significant gap.

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 sentence that front-loads the action and resource, with no superfluous words. It is concise and efficiently communicates the core operation.

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 relatively simple reorder operation, the schema is clear, but the description lacks important behavioral context such as whether all templates must be provided, what happens with duplicate positions, or error handling. Since there are no annotations and no output schema, the description should cover these aspects but does not.

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?

The schema provides 100% coverage with descriptions for both 'uuid' and 'viewPosition'. The description essentially restates the schema's purpose without adding extra semantics, such as validation rules, default behavior, or interaction between items. Baseline 3 is appropriate.

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 clearly states the action 'Reorder' and the resource 'subscription templates', and specifies the input mechanism ('by providing each template UUID with its new position'). It is distinct from other reorder tools by explicitly naming the resource.

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?

The description implies when to use the tool based on the verb and resource, but does not provide explicit guidance on when to choose it over alternatives or when not to use it. No exclusions or comparisons are mentioned.

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