reorder_accounts

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

With no annotations to cover safety or side effects, the description carries the full burden but only states the action. It does not disclose whether the provided order fully replaces the existing order, how invalid IDs are handled, or whether the change is persistent or reversible.

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 a single, front-loaded sentence that avoids unnecessary words. It is concise but minimally informative; it could include more useful context without becoming verbose.

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 tool with one parameter and full schema coverage, the description is mostly adequate, clearly stating the core function. However, the lack of annotations or any behavioral caveats leaves questions about mutation semantics unanswered, making it incomplete for an autonomous agent.

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 already covers the parameter at 100%, describing 'account_ids' as an 'Ordered array of account IDs'. The description adds the context of 'display order', which slightly clarifies the purpose but does not provide additional syntax or format details beyond the schema.

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 uses the specific verb 'Update' and identifies the resource as 'display order of accounts', making the tool's purpose clear. It distinguishes itself from account CRUD tools by focusing on ordering rather than account data, though it could be more explicit about the reordering semantics.

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 offers no guidance on when to use this tool versus alternatives, such as whether it is the sole mechanism for reordering accounts or if any prerequisites exist. It simply states the function without contextualizing its place among account-related tools.

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