List_SharePoint_Folders

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

No annotations are provided, so the description bears full responsibility for behavioral disclosure. It states 'list all sub-folders' but does not clarify if this includes nested sub-folders (recursive vs flat), permissions required, rate limits, or return format. This ambiguity limits transparency.

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 sentences with no waste: the first sentence states the purpose, the second adds parameter usage details. It is front-loaded and efficient.

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?

Given one parameter, no annotations, and no output schema, the description is fairly complete for a list tool but lacks details on output structure (e.g., folder names only or metadata) and whether the list is recursive. It is adequate but could be fuller.

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 input schema has 0% description coverage, but the description adds significant value by explaining that the parent_folder parameter can be None/null/empty for the document library root and clarifies what root means for Graph API. This goes beyond the schema's type and title.

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 lists all sub-folders in a SharePoint directory, distinguishing it from sibling tools like List_SharePoint_Documents and Get_SharePoint_Tree. It specifies the exact resource (SharePoint directory) and action (list sub-folders), with additional context on handling the root.

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 guidance on how to use the parent_folder parameter (None/null/empty string for root) but does not explicitly state when to use this tool vs alternatives like Get_SharePoint_Tree for hierarchy or List_SharePoint_Documents for files. Usage is implied but not directly contrasted.

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