move_user_credential_after

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

The description only states the basic action without disclosing behavioral traits such as required permissions, error conditions, side effects (e.g., whether reordering is persistent or reversible), or constraints on reordering. With no annotations provided, the description carries the full burden and falls short.

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 sentence, making it concise, but it is too terse for a tool with four parameters and a specific ordering operation. It lacks structured elements like bullet points or examples that could improve clarity without adding excessive length.

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?

Given the absence of an output schema and annotations, the description is incomplete. It does not explain what happens upon success or failure, whether the operation is idempotent, or how it interacts with credential states. The sibling tool 'move_user_credential_to_first' suggests a family of reordering operations, but the current description does not contextualize its role.

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% with clear parameter descriptions. However, the tool description adds no additional semantic meaning beyond what the schema already provides. It does not explain the ordering logic, such as whether 'after_credential_id' must exist or how ties are handled. 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 verb 'Move' and the resource 'user credential', indicating reordering. However, it does not differentiate from the sibling tool 'move_user_credential_to_first', which performs a similar reordering but to the first position. The parameter 'after_credential_id' implies the specific ordering, but the description could explicitly clarify this distinction.

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?

No guidance is provided on when to use this tool versus the sibling 'move_user_credential_to_first' or other credential management tools. The description lacks context about typical use cases, prerequisites, or conditions that dictate its usage.

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