list_document_folders

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

No annotations provided, so description carries full burden. It discloses auth fallback and resource availability rollout. However, it does not describe pagination behavior (page_size, page_number), ordering, or return format details beyond names and IDs. Somewhat adequate but could add more behavioral context.

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?

Two sentences; first states core purpose, second adds essential auth context. No fluff, front-loaded with key info.

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?

Lacks output schema. Description explains purpose and auth but falls short on return format details (e.g., structure of response), error handling, and pagination behavior. For a 4-parameter tool, more completeness would be expected.

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 coverage is 100% (all params have descriptions). Description adds minimal value beyond schema: only mentions return of names and IDs but doesn't clarify param roles. Baseline 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?

Clearly states it lists document folders for an organization, returning names and IDs. Distinguishes from sibling tools like list_document_sections which list sections, not folders.

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?

Provides context on when to use (works with API key on tenants with Document Folders resource, rolling out in 2026). Describes fallback auth (JWT) when API key is rejected. Lacks explicit comparison to sibling tools but gives useful operational guidance.

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