perch_list_src

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

No annotations are provided, so the description carries the behavioral burden. 'List' conveys a read-only, non-destructive operation, and 'with sizes' hints at the return content, but it does not explicitly state safety, permissions, or side-effect absence. For a zero-parameter listing tool this is adequate but minimal.

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?

A single front-loaded sentence with no filler. It states the action, scope, and return detail in one pass, earning every word.

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 zero-parameter, simple listing tool with no output schema, the description is nearly complete: it identifies what is listed and mentions that sizes are included. It could go slightly further in describing the return format or clarifying 'srcManifest' for an unfamiliar agent, but no critical invocation detail is missing.

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 tool takes zero parameters, and the schema is correspondingly empty. Per the rubric, zero parameters yield a baseline of 4; there are no parameter semantics needing further explanation.

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 names a specific verb ('List'), a precise resource ('src/ files in the generator's srcManifest'), and an additional output dimension ('with sizes'). It is easily distinguished from siblings like perch_src or perch_upload_src, which operate on source files rather than listing the manifest.

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?

There is no explicit guidance on when to use this tool instead of alternatives such as perch_src or perch_grep, nor any exclusions. The phrase 'all src/ files' implies scope but does not constitute usage guidance.

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