move_items_to_bin

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

With no annotations, the description carries the full burden of behavioral disclosure. It only states the operation name and does not mention side effects (e.g., whether items are removed from their original bin), required context (e.g., selected items, active bin), or any advanced behavior implied by 'expanded operation'.

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 short sentence, which is concise, but it is under-specified rather than efficiently informative. It omits critical details and does not earn its place because it only restates the tool name in prose.

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?

The tool is a mutation operation with no annotations, no output schema, and an unhelpful schema. The description fails to explain what 'expanded operation' means, what inputs are needed, or the effect of the move. It is inadequate for an agent to select and invoke the tool correctly, especially given the large sibling tool list.

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 is nearly empty (additionalProperties: {}), so there are no explicit parameters. The description does not clarify how to specify which items or which target bin, nor does it mention using currently selected items. The 0-param context is thus not compensated by any textual explanation, leaving the invocation ambiguous.

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 action ('move') and the resource ('items to bin'), which is more specific than a bare name. However, it does not distinguish this from the sibling 'move_item_to_bin' beyond the plural 'items', and the phrase 'expanded operation' adds little clarity.

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?

There is no guidance on when to use this tool versus alternatives, such as when moving multiple items versus a single item. No context, prerequisites, or exclusions are provided. The plural in the name hints at multiple items, but the description does not explicitly state this.

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