list_files

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

No annotations are provided, so the description must fully disclose behavior. It states it lists files and returns URLs, but omits any side effects, permissions, pagination, or rate limits. The operation appears read-only but is not confirmed, leaving behavioral gaps.

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 short, consisting of two sentences and an args list. It is efficient and front-loaded with the core purpose. However, the formatting is plain and could be improved for readability.

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 requires one parameter and has an output schema (not shown), the description should clarify the scope of 'files and documents' and any default ordering or filtering. It lacks these details, making it incomplete for an agent to use confidently.

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?

With 0% schema description coverage, the description must compensate. It only adds 'School ID' to the parameter name, providing minimal additional meaning. It does not explain what constitutes a valid school ID or how to obtain it.

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 'list files and documents posted for a school', specifying a verb and resource. It mentions returning file URLs for download_file, which gives some context. However, it does not differentiate from other list_* siblings like list_forms or list_schools, lacking explicit distinction.

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 no guidance on when to use this tool versus alternatives. The only hint is 'returns file URLs for download_file', which implies a follow-up action but does not state when to choose this over other list or retrieval tools.

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