Excel List Workbooks

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

Annotations already declare readOnlyHint=true and destructiveHint=false, so the safety profile is covered. The description adds the file extension filter and target folder, but does not disclose behaviors like pagination, recursion depth, or whether it returns full metadata. This adds some context beyond the schema and annotations, but not rich behavioral detail. No contradiction with annotations.

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, front-loaded sentence that states the action, resource, and scope with no wasted words. It is appropriately concise and immediately informative.

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 tool has three optional parameters fully documented in the schema, annotations cover safety, and an output schema exists, so return-value explanation is unnecessary. The description covers the core purpose and target folder. It might benefit from a note about permission requirements or that it only lists metadata, but these are minor given the available structured information.

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%: all three parameters (site_id, drive_id, folder_path) have descriptions in the schema, so the baseline is 3. The tool description does not add additional semantics, such as how site_id and drive_id relate or how to obtain them. It adds no value beyond what the schema already provides.

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 verb 'List' and the resource 'Excel workbooks (.xlsx, .xls)', with the target location 'OneDrive or SharePoint folder'. This is specific and distinguishes it from sibling tools that create tables, workbooks, or manipulate rows. An agent can immediately understand its role without ambiguity.

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: when you need to list Excel workbooks in a folder. However, it does not explicitly state when to use this tool over alternatives, mention prerequisites (e.g., site_id/drive_id requirements), or note that it is read-only compared to other operations. The usage context is clear but not elaborated with exclusions or alternatives.

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