Pilot MCP

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 but fails to state whether the operation overwrites existing files, preserves metadata, handles directories, or requires specific permissions. The mutation nature is implied but not detailed.

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 extremely concise at only five words. There is no redundant or filler text; every word directly contributes to understanding the tool's function.

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?

For a file mutation operation with no output schema and no annotations, the description is insufficient. It fails to explain how to specify source and destination paths (critical for a move operation), success indicators, or side effects such as broken sharing links.

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?

The input schema contains zero parameters, which establishes a baseline score of 4 according to the evaluation rubric. The description does not need to compensate for missing schema documentation since there are no parameters to describe.

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 identifies the core action ('Move or rename') and the target resource ('file in OneDrive'), distinguishing it from sibling operations like delete, read, or write. However, it does not clarify the relationship between moving and renaming or specify path requirements.

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 copying and deleting, or when renaming in-place is preferable to moving. It lacks prerequisites (e.g., file existence checks) and error condition handling.

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