Sort Sharelist

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

Annotations indicate destructiveHint=true and idempotentHint=true. The description confirms it returns an upstream API response on success but does not elaborate on side effects, error cases, or the permanence of the reordering. It adds some context beyond annotations but lacks detail.

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 extremely concise—two sentences that front-load the main action and then explain input and return. No unnecessary words or repetition.

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 two parameters and no output schema, the description covers the core functionality, input semantics, and return type. It could mention that the sharelist ID refers to a community sharelist (title says 'Sharelist' but description specifies 'community sharelist'), but overall it is adequate.

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 description adds valuable semantic context by explaining that the symbols array should be provided in the desired new order. This goes beyond the schema descriptions, which only state 'Sharelist ID' and 'Security symbols'. The ordering requirement is clarified.

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 tool's purpose: reordering securities in a community sharelist by providing a new order of symbols. It uses a specific verb ('Reorder') and resource ('sharelist by id'), and distinguishes from sibling tools like sharelist_add and sharelist_remove.

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 does not provide any guidance on when to use this tool versus alternatives such as sharelist_add, sharelist_remove, or sharelist_create. There is no mention of prerequisites, context, or exclusions.

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