List For Folder

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

Annotations already declare readOnlyHint=true, so no safety concerns. However, the description adds no behavioral traits beyond this. It does not explain behavior when path is null, response limits, or pagination, which are critical for an agent to understand the tool's behavior.

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 concise sentence with no wasted words. However, it is too sparse for a tool with multiple parameters and an output schema; a bit more structure (e.g., listing primary use) would improve effectiveness.

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 the tool has two optional parameters, an output schema, and annotations, the description is incomplete. It fails to explain how the optional 'path' default value affects behavior (e.g., listing all folders when null) or the role of 'fields' beyond a brief schema note. The agent lacks sufficient context to use the tool reliably.

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%, so baseline is 3. The description does not add meaning beyond the schema; for example, it does not clarify the format of 'path' or how 'fields' affects output. The schema descriptions already provide basic info, but the tool description offers no additional semantic value.

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 'List Folders by Path' clearly indicates a read operation listing folders using a path parameter. It distinguishes from sibling tools that list other entities (e.g., users, groups). However, it lacks specificity on what 'by Path' entails (e.g., listing contents or matching path pattern).

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?

No guidance is provided on when to use this tool versus alternatives. There is no mention of context, prerequisites, or exclusion conditions, leaving the agent to infer usage from the name alone.

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