moveProjectAction

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

No annotations are present, so the description must fully disclose behavioral traits. It only states that the project is moved, but fails to detail side effects (e.g., whether it changes the location field, requires permissions, is reversible, or triggers other operations). This is insufficient for a mutation tool.

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 (one sentence) and to the point. It is concise, but it could be improved by including key behavioral details without adding much length.

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 (mutating tool with a nested requestBody parameter, no output schema, no annotations), the description is incomplete. It does not explain what 'location' means, acceptable formats, or the impact on the project's data.

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% with descriptions for both parameters. The tool description adds no additional parameter meaning beyond the schema. However, note a potential inconsistency: the schema describes 'location' as 'Location of the new Project to be created', which may be misleading for a move operation.

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 'Moves project to a different location' clearly states a specific action (move) on a resource (project). It distinguishes itself from siblings like moveFromDocument and moveToDocument, which operate on documents, by specifying project as the target.

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 usage guidance is provided. The description does not specify when to use this tool versus alternatives (e.g., patchProject for updating other project fields, or createProject for new projects), nor does it mention any prerequisites or limitations.

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