onedrive_set_scope

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

No annotations are provided, so the description must convey behavioral traits. It states the action but does not disclose any side effects, reversibility, required permissions, or what 'restricting access' entails beyond a vague folder reference.

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 a single, concise sentence with no extraneous information. Every word contributes to the core purpose.

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 no output schema, no annotations, and a simple action, the description is incomplete. It lacks details about how the folder is determined, whether the change is persistent, and how to revert the restriction.

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 has 0 parameters and 100% coverage, so the description adds no parameter-level depth. However, the description implies a 'specific folder' but no parameter exists, which could cause confusion. Baseline for 0 parameters is 4, but this potential mismatch reduces clarity.

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 action ('restricts LMPC's OneDrive access to a specific folder') using a specific verb and resource. However, it does not distinguish this tool from sibling tools like onedrive_root or onedrive_list_files, which also deal with OneDrive scoping.

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 other OneDrive tools. There are no exclusions, prerequisites, or context about expected usage scenarios.

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