post_knowledge_base_move_route

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

Annotations already declare readOnlyHint=false, idempotentHint=false, and destructiveHint=false, so the agent knows this is a mutating, non-idempotent operation. The description adds no behavioral context beyond that, such as whether the move is reversible, what happens if the target folder is missing, or what permissions are needed.

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 very short and front-loaded, but it is a fragment that omits essential context rather than a tight, complete statement. It avoids waste but is under-specified for a mutation tool.

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 that this is a mutating tool, has 50% schema coverage, no output schema, and a closely related bulk-move sibling, the description is not complete. It fails to specify what entity is being moved, what a folder is in this context, or any return/error behavior.

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 50%: document_id is documented in the schema, while move_to has no schema description. The description's 'To Folder' phrase weakly maps to move_to as the destination, but it does not clarify the expected format or valid values, so it only minimally compensates for the 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 gives a verb (Move) and a destination (To Folder), but the resource is stated vaguely as 'Entity' rather than specifying a knowledge base document or folder. It does not distinguish this singular move from the sibling bulk move tool post_knowledge_base_bulk_move_route.

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, no prerequisites, and no exclusions. The description only restates the basic action.

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