list_files

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

With no annotations, the description carries full responsibility. It discloses the action (listing files) and the return type (dictionary with files and metadata), but it does not mention permissions, error behavior, or pagination. For a simple read-only tool, it's adequate but not rich.

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 concise and structured into Args and Returns sections, with each sentence adding value. It is front-loaded with the primary purpose and does not waste words.

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 tool with only two parameters and no output schema, the description covers the essential context: what it lists, the parameters, and the return format. It lacks edge-case details (e.g., record not found), but that is acceptable given its simplicity.

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 0%, so the description must explain parameters. It provides meaningful explanations for both 'record_id' ('The ID of the Zenodo record') and 'include_metadata' ('Whether to include file metadata'), going beyond the schema's bare names.

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's function: 'List all files available in a Zenodo record.' It uses a specific verb ('list') with a specific resource ('files in a Zenodo record'), and it distinguishes from siblings like search_records and get_metadata by focusing on file listing.

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 implies usage context (when you need to see files in a Zenodo record) but does not explicitly contrast with sibling tools or provide exclusions. It does not say when to prefer this over search_records or get_metadata, but the purpose is distinct enough to infer.

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