submit_site_move

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

With no annotations, the description carries full burden for behavioral disclosure. It only states the tool submits a request and raises an error on failure, but lacks details on mutability, permissions, idempotency, or side effects. The 'self' parameter is not explained, further reducing transparency.

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 concise with a single line for the action and structured arg list. However, it sacrifices necessary detail for brevity, making it merely adequate. It is front-loaded but incomplete.

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 complexity (3 required params, one with nested object and enums) and lack of annotations, the description is incomplete. It omits output behavior, prerequisites, and detailed parameter explanations, making it insufficient for reliable agent use.

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 compensate. It briefly describes site_url as 'the URL of the site' and settings as 'move configuration', but fails to explain the structure of settings (Date, MoveScope, MoveType, SourceUrl, TargetUrl) or the self parameter. This superficial treatment is insufficient for correct invocation.

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 'Submit a site move request.' using a specific verb and resource. It effectively distinguishes from sibling tools like get_site_moves, which is a read operation, and other tools unrelated to site moves.

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 provides no guidance on when to use this tool versus alternatives, such as get_site_moves for retrieving existing moves. No conditions, prerequisites, or exclusions are mentioned, leaving the agent without contextual decision support.

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