get-my-drive-item

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

Annotations already indicate readOnlyHint=true, idempotentHint=true, and destructiveHint=false, so the safety profile is covered. The description adds one useful behavioral detail beyond annotations: the downloadUrl inclusion for files. It does not however describe folder behavior, response shape, or any limitations, which would be valuable without an output schema.

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 sentence that gets straight to the point, with no wasted words. It is front-loaded with the action and resource.

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 one-parameter, read-only metadata retrieval tool with rich annotations, the description is mostly complete. It names the resource and a key return detail (downloadUrl). The main gaps are lack of guidance on itemId provenance and no explicit distinction from the download-focused sibling tools, but the low complexity keeps this from being a major deficiency.

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 100% with a single itemId parameter, so the schema carries most of the parameter burden. The description does not explain how itemId should be obtained or how file versus folder behavior affects the call, but it also does not need to compensate heavily given the simple input schema.

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 states a specific verb ('Get'), a clear resource ('OneDrive file/folder metadata'), and adds a useful distinguishing detail about @microsoft.graph.downloadUrl for files. It is clear on its own, though it does not explicitly contrast with sibling tools like get-drive-item or get-my-drive-item-download-url.

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 closely related siblings such as get-drive-item, download-my-drive-item, get-my-drive-item-download-url, or the list-my-drive-* tools. The description does not state any selection criteria or exclusions.

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