Move an item into or out of a folder

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

Annotations already indicate a non-destructive write (readOnlyHint=false, destructiveHint=false). The description adds the HTTP method (POST) and authorization class (board_or_agent), which provides transparency about how the operation is performed. No contradictions with annotations. The behavioral trait of 'moving' is disclosed, but no further details about side effects (e.g., metadata preservation) are given.

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, consisting of two short sentences that front-load the purpose. No extraneous information. It efficiently communicates the core action and necessary operation details.

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 description omits important context: the types of items that can be moved (routine, skill), the effect of providing null folderId (removing from folder), and the tool's output (though an output schema exists). Given the complexity of the input schema (nested object with optional fields), the description is insufficient for an agent to correctly select and invoke this tool without relying solely on schema inspection.

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 description coverage is 0%, so the description must explain parameters, but it does not. It fails to mention that 'kind' accepts routine/skill, that 'itemId' is a UUID, or that 'folderId' is optional (null means remove from folder). The agent must infer all meaning from the schema structure and property names, leaving a significant semantic gap.

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 moves an item into or out of a folder, specifying the verb (move) and resource (item/folder). It distinguishes from sibling folder operations like creating, updating, or deleting folders, as well as moving folders themselves (e.g., pc_post_companies_by_company_id_folders_by_folder_id_move).

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 alternatives. There is no mention of when to move an item vs. when to use other folder operations, or what prerequisites (e.g., target folder existence) are needed. The context of the move (into/out of a folder) is implied but not explicitly contrasted with sibling tools.

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