listOfficeDocs

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

No annotations are provided, so the description carries the burden. It discloses the read-only nature ('Retrieves a list') and the ordering behavior, but lacks details on pagination, whether subfolders are included, or any access requirements. This is adequate but not rich.

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, well-structured sentence that uses every word efficiently. It is front-loaded and immediately conveys the tool's purpose and ordering.

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?

The description is adequate for a simple listing tool with a single optional parameter, but since no output schema is present, it does not clarify the shape of the returned items (e.g., field names, types). It also does not mention related tools for alternative retrieval patterns, leaving some selection ambiguity.

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 schema already provides 100% coverage for the single parameter folderId, including its optionality and default behavior. The description adds no additional parameter context beyond what the schema states, so baseline score of 3 applies.

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 ('Retrieves a list'), the resource ('Office documents and folders from OneDrive'), and a distinguishing detail ('ordered by last modified date'). This differentiates it from siblings like listGoogleDocs and readOfficeDoc.

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 implies usage for listing items from a folder or root, but does not explicitly state when to use this tool over alternatives like searchOfficeDocs or recentOfficeDocs. No exclusions or alternative references are provided.

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