list_project_files

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

The description implies read-only behavior ('List'), but lacks details on recursion behavior (though subdirectory parameter hints), error handling for invalid paths, or whether all file types are included by default. Without annotations, the description covers basic behavior but not comprehensively.

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 short sentence with no redundancy, though it could benefit from a bit more structure (e.g., stating the required parameter). It is efficient but not overly terse.

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?

Without an output schema, the description does not specify what the tool returns (e.g., file names, full paths, metadata). The tool has three parameters and moderate complexity, but the description omits important context for an agent to use it effectively.

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?

All three parameters have descriptions in the input schema (100% coverage), so the baseline is 3. The description adds no extra meaning beyond 'optionally filtered by extension', which is already captured in the schema.

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 states the verb 'List' and resource 'project files', with an optional filter by extension, clearly distinguishing it from sibling tools like 'list_projects' which lists projects, not 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?

No usage guidelines are provided. There is no indication of when to use this tool versus alternatives, nor any prerequisites or exclusions.

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