list_files

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

With no annotations, the description carries the full burden, and it discloses three non-obvious traits: results are ordered newest first, the returned links are freshly minted and expire, and a Blob store connection is required. It omits auth requirements and anything about pagination beyond the limit cap already in the 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?

A single dense sentence front-loads the resource and scope, then appends the two operational caveats (link expiry, Blob store requirement). Nothing is padded and nothing important is buried.

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?

For a two-optional-parameter read tool with 100% schema coverage and no output schema, the description supplies what the schema cannot: ordering, link volatility, and the connection prerequisite. Return-value detail beyond 'links' is thin, but adequate for this complexity level.

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%, so 'kind' and 'limit' are already documented with enum values, defaults, and bounds. The description only restates the media kinds and the newest-first ordering, which the schema already conveys — 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?

Specific verb (list) plus a tightly scoped resource — the media assets this connector previously generated — with ordering ('newest first') and payload shape ('fresh private links'). It is easily distinguished from siblings like list_models, which enumerate models rather than generated files.

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?

Names a hard prerequisite ('Needs a connected Blob store'), which tells the agent when the call is even viable, and implies the retrieval use case for prior outputs. It does not name an alternative or an explicit when-not-to-use condition, but no sibling competes for this job.

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