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

The annotations already declare mutation, idempotency, and destructive hints. The description adds useful behavioral context by stating that the resulting order is reflected everywhere the list appears, including `statuz accounts list`, the Mac app, and the composer.

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?

Two tight sentences, front-loaded with the action and followed by the cross-surface effect. There is no redundant or wasted 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 simple reorder operation, the description, annotations, and fully described schema together cover the essentials. The description could clarify the destructive annotation or output behavior, but no output schema exists and the core effect is stated.

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 100%, so the schema already documents all three parameters. The description mentions moving up or down the list but adds no additional parameter syntax or constraints beyond what the schema provides, so the baseline 3 applies.

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 gives a specific verb and resource: "Move an account up or down the list." It clearly conveys reordering rather than listing, removing, or setting a default, but it does not explicitly name or distinguish against siblings like accounts_default.

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?

It implies that the tool is for reordering an account, but offers no explicit when-to-use guidance, prerequisites, or alternatives. It never says when to use accounts_move versus accounts_default or accounts_list.

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