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

Annotations already declare readOnlyHint=true and destructiveHint=false, so safety is covered. The description contributes real behavioral context beyond that: the page-at-a-time contract and the instruction to feed nextPageToken back as pageToken. It stops short of describing what a page entry contains, which it could since there is no output schema.

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?

Three sentences, zero filler, with the core behavior front-loaded and the pagination and sibling-routing details following in priority order. Every clause earns its place.

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?

With no output schema, the description usefully explains that results come one page at a time and names the nextPageToken continuation field. It does not describe the shape of returned entries or error conditions, leaving a modest gap for a listing tool, though nothing critical to correct invocation is missing.

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 the baseline is 3, but the description adds cross-parameter workflow meaning the schema cannot state on its own: the nextPageToken-to-pageToken round trip and the default one-level vs recursive listing mode. This materially improves correct invocation of pageToken and recursive.

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?

States a specific verb and resource ('Lists objects and sub-folders under a prefix') plus the pagination constraint, so the agent knows exactly what it does. It also names the sibling tools it is not (find_objects, stat_prefix), making differentiation immediate.

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?

Explicitly routes alternatives: search by name or total a prefix goes to find_objects or stat_prefix 'rather than paging through it here.' It also states the default depth behavior and how to change it, so the when-to-use and when-not-to-use conditions are both covered.

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