move_party

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

With no annotations provided, the description carries the full burden of behavioral disclosure. It states the tool updates location data, implying a mutation, but lacks details on permissions, side effects (e.g., if movement triggers events), rate limits, or error conditions. This is inadequate for a tool with multiple parameters and no structured safety hints.

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 brief and front-loaded, consisting of a single sentence that directly states the tool's function. There is no wasted verbiage, though it could be more structured with separate clauses for context or usage.

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 (6 parameters, mutation tool), lack of annotations, and no output schema, the description is insufficient. It omits critical details like return values, error handling, interaction with game state, and how it differs from similar tools, leaving significant gaps for an AI agent to operate effectively.

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 for undocumented parameters. It mentions 'world map coordinates or POI' and 'location name and optional POI reference', which loosely maps to targetX/targetY, locationName, and poiId, but fails to explain partyId or sessionId, leaving 2 of 6 parameters without semantic context.

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 verb ('Move') and resource ('a party'), specifying the action of relocating a party to coordinates or a POI. It distinguishes from siblings like 'move_character_to_room' by focusing on party-level movement on a world map, though it doesn't explicitly compare to alternatives like 'travel_to_location'.

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 'travel_to_location' or 'update_party'. The description mentions the action but offers no context about prerequisites, constraints, or typical scenarios for invocation.

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