Move Catalog

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

The description notes that it 'Creates a new Cost Catalog records' and returns HTTP 201, but it does not explain whether the original catalog is deleted or modified, nor does it cover permissions or side effects. Annotations show readOnlyHint=false but the description lacks details beyond basic mutation.

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 reasonably concise with three sentences plus API reference. It front-loads the action. The inclusion of endpoint details is useful but slightly verbose; still efficient overall.

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?

No output schema is provided, but the description mentions the return type (created object on HTTP 201). It does not explain the move semantics fully, such as whether the original record is retained or deleted, nor does it cover error conditions or prerequisites. Adequate but with gaps.

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 100% and the schema already describes each parameter. The description only repeats the required parameters without adding new semantic information like examples, format, or constraints. Baseline 3 applies.

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 explicitly states 'Moves Catalog under Parent Catalog' and identifies it as a move action on Cost Catalog records. The verb 'move' is specific and distinguishes it from sibling tools like create_catalog or delete_catalog.

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 such as create_catalog or delete_catalog. The description lacks any context for when the move operation is appropriate or when it should be avoided.

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