promote_basket_item

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

With no annotations, the description must disclose behavioral traits. It notes refusal on private items but does not clarify whether the operation is a move (destructive) or copy, what happens on overwrite, or any permission requirements. These are gaps given the absence of annotations.

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 remarkably concise yet complete. It front-loads the main action in the first sentence, adds the critical restriction on private items in the second, and includes parameter descriptions in clear bullet format. No superfluous words.

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 tool has an output schema, the description does not need to explain return values. The description covers the core behavior and restrictions. It could mention potential overwrite behavior or whether it moves vs copies, but overall it is sufficient for selecting and invoking the tool.

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 0%, so the description must explain parameters. It does so effectively: source_path as 'Absolute path to the file in basket/' and target_path as 'Absolute destination path (file or folder)'. This adds value beyond the parameter names.

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 a basket item to a stable project folder') and the resource ('a basket item'). The verb 'promote' and context 'from basket to active storage' distinguish it from sibling tools like list_basket or add_tracked_file.

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 explicitly mentions that it 'Refuses to touch basket/private/ items', which guides when not to use it. It implicitly states usage for promoting non-private basket items to stable storage. While no explicit alternatives are given, the note on private items provides clear boundary.

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