get_item_metadata

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

No annotations exist, so the description carries the burden: it discloses the exact return shape, declares the operation's read nature implicitly, and surfaces a non-obvious security decision (downloadUrl withheld per SECURITY_REVIEW N-M2). It omits error behavior for invalid paths/ids and any permission requirements.

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?

Front-loaded purpose sentence, then Args and Returns blocks with zero filler; the return-field enumeration earns its place because no output schema exists. Slightly list-heavy, but nothing is redundant.

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?

With no output schema, the explicit return-field list is essential and present, as is the parameter dual-form explanation. The remaining gap is failure modes — what happens on an unresolvable path or missing item — which an agent would need before calling confidently.

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%, and the description fully compensates by defining the single parameter's two accepted forms with a concrete path example ('/Documents/foo.pdf') and the raw Graph drive item id alternative — information available nowhere else.

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?

States a specific verb and resource ('Get full metadata for a single OneDrive file or folder'), and the word 'single' plus the plural siblings (search_onedrive, list_folder) makes the scope distinction clear without opening any schema.

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?

Explicitly routes content retrieval to download_file() and explains why the downloadUrl is omitted, so the agent knows when to reach for another tool. It does not address when to prefer get_drive_info or how to handle a not-found path, so it stops short of full when/when-not coverage.

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