list_project_files

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

With no annotations, the description carries the behavioral burden. It clarifies that the tool returns file names only, not contents, and explains the prefix filtering behavior. However, it does not disclose potential limitations such as pagination, sorting, or error behavior, but for a simple read-only list this is acceptable.

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 two concise sentences, leading with the core action and then the optional filter. No extraneous detail.

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 listing tool with good schema coverage and no output schema, the description is nearly complete. It omits details like return ordering or whether file extensions are included, but these are minor and the core behavior is clearly stated.

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 input schema already provides descriptions for both parameters (100% coverage), including the prefix filter with examples. The description adds little beyond restating the prefix filter, so the schema carries the semantic weight. Baseline 3 is appropriate.

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 the specific verb 'List' and names the resource 'YAML file names in a FlutterFlow project.' It also mentions an optional prefix filter, which differentiates it from siblings like list_pages (which likely lists only pages) and search_project_files (which searches content).

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 states the tool lists all YAML file names and supports an optional prefix filter, giving enough context for when to use it. However, it does not explicitly mention alternatives or when not to use it, e.g., if looking for page-specific listings, so it falls short of explicit guidance.

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