list_files

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

There are no annotations provided, so the description carries the full burden of behavioral disclosure. It only states the basic action and scope, but does not explain whether pagination is used, what permissions are required, what fields are returned, or how this differs from related file tools.

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 that states the action and object clearly. There is no redundant information or filler, making it well-structured and easy to parse.

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 simple list operation with one parameter and no output schema, the description provides a minimal level of completeness. However, it lacks details about return values, pagination, or any behavioral nuances, which would be helpful given the absence of annotations and output schema.

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?

The schema has a single required parameter, school_id, with no description in the schema (0% coverage). The tool description mentions 'for a school,' which weakly ties to the parameter, but the description does not explicitly explain that school_id refers to the school whose files should be listed. The parameter name is fairly self-explanatory, keeping this at an acceptable level.

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 uses a specific verb ('List') with a clear resource ('files and documents') and scope ('posted for a school'). This distinguishes it from sibling tools such as download_file or list_photos, making the purpose immediately clear.

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 clearly implies when to use this tool: to retrieve files and documents associated with a school. However, it does not explicitly mention when not to use it or any alternatives, such as download_file for retrieving a specific file.

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