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

With no annotations, the description carries the behavioral burden and successfully discloses key traits: order equals index, unknown IDs are skipped, and the updated collection list is returned. It does not cover permissions, idempotency, or partial-list effects, but it is substantially transparent for a mutation tool.

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 description is four short sentences, front-loaded with the core action, and each sentence adds useful operational detail. There is no redundant or filler text.

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 two-parameter reorder mutation with no annotations and no output schema, the description covers the action, parameter behavior, unknown-ID handling, and return value. Missing authorization requirements and behavior when only a subset of known IDs is provided are the main remaining gaps.

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 100%, so the schema already documents both parameters and establishes a baseline of 3. The description adds meaningful semantics beyond the schema by explaining that each ID is assigned order equal to its index and that all collection IDs should be passed.

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 names a specific verb and resource: reorder collections within a site. No sibling tool performs reordering, so the purpose is immediately distinguishable from Create_Collection, Update_Collection, and List_Collections.

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 it by instructing the caller to pass all collection IDs in the desired order. However, it does not explicitly compare against alternatives like Update_Collection or state when not to use this tool.

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