list_files

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

No annotations are provided, so the description must carry the behavioral health. While it states 'Returns file URLs', it does not disclose whether the operation is read-only, requires special authorization, or handles availability or pagination. This gives the agent little insight into side effects or assumptions.

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 sharp and to the point, with no extra filler. The opening sentence immediately states what the tool does, and the argument listing is useful, though it adds no new information. It could benefit by moving the Args line directly beneath the purpose, but overall it is appropriately succinct.

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's simplicity (one parameter, straightforward output), the description gives a functional starting point. However, it omits potentially important context such as what range of dates is covered, whether the list is paginated, or what types of files/documents are included. With an output schema present, return values are not An issue here, but the usage context remains thin.

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%, and the description only repeats the parameter name and a generic label ('school_id: School ID') without adding meaningful guidance. It does not explain how to obtain the school_id, its format, units, or relationship to other data, so added value beyond the schema is nonexistent.

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 explicitly states 'List files and documents posted for a school', identifying a clear verb, resource, and scope. It differentiates from sibling tools like list_links and list_photos by specifying 'files and documents', making the purpose immediately comprehendible.

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 provides some usage context by noting that it returns file URLs for download_file, implying when to use it. However, it does not explicitly mention alternatives or give conditions such as 'use get_post to fetch files attached to a single post', so the guidance remains implicit.

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