list_react_files

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

No annotations are provided, so the description carries the full burden. It clearly states the read-only operation (lists files) and the output includes line counts, but it does not disclose whether the project must be loaded, how paths are formatted, or if results are sorted. Still, for a simple list tool, the basic behavior is transparent.

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, front-loaded sentence that conveys the essential information without any filler. Every word earns its place, making it appropriately concise and well-structured.

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, the description covers the core functionality (file extensions and line count). It lacks explicit mention of the loading prerequisite, but the schema's parameter description implies the project is loaded. Without an output schema, the return format is not fully specified, yet the description is sufficient for a simple listing tool.

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 coverage is 100% with the 'name' parameter described as 'Name or path of the loaded project'. The tool description adds no extra meaning beyond referencing 'project', so it does not enhance the parameter semantics beyond the schema's baseline.

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 'Lists' with a clear resource: '.tsx/.jsx/.svelte files' and adds the relevant detail of 'line count'. This clearly distinguishes it from sibling tools like 'list_files' (generic) and 'list_react_components' (components, 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?

The description provides no guidance on when to use this tool versus alternatives. It does not mention list_files, list_react_components, or any other sibling, nor does it state any exclusions or prerequisites beyond the implicit 'project' context.

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