Get SharePoint Library Item

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

With no annotations, the description carries the full burden. It clearly states the operation is read-only ('Read metadata'), covers both files and folders, and declares the required permission. It does not mention response format or potential errors, but for a simple read operation this is adequate.

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 two concise sentences. The first sentence states the core purpose, the second provides the permission requirement and Chinese intents. Every part serves a purpose, with no redundancy.

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 low-complexity tool with two fully described parameters and no output schema, the description is reasonably complete. It covers the purpose, permission, and scope (file or folder). It does not detail return fields, but the term 'metadata' is self-explanatory for a get operation.

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%, so the parameters are already well-documented. The tool description does not add additional meaning beyond the schema, such as how the parameters relate or example values. Baseline of 3 is appropriate.

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 tool reads metadata for a SharePoint document-library file or folder, using the specific verb 'Read' and resource type. It distinguishes from siblings like sharepoint_download_file (which downloads content) and sharepoint_list_drive_items (which lists items).

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?

The description provides clear context that this tool is for reading metadata, and it also mentions the required permission (delegated Files.Read.All). However, it does not explicitly mention alternatives or when not to use it, such as for downloading content, so it falls short of a 5.

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