list_seed_files

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

Tool is a simple read operation with no annotations. Description doesn't disclose any side effects or permissions, which is acceptable for a listing tool but adds no extra transparency beyond the obvious.

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?

Description is extremely concise and front-loaded. However, it could be slightly more structured by including parameter details.

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 (one optional param, no output schema), the description is minimally adequate but incomplete due to missing parameter explanation.

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?

Single parameter 'target' with enum values is not mentioned in description. With 0% schema coverage, description should explain the parameter and its filtering capability, but it only says the tool lists files in both directories.

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?

Description clearly states verb 'Lists' and resource 'SQL files' with specific directories 'base/ and data/'. Name matches purpose, and it distinguishes from sibling list tools like list_files and list_tables.

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 guidance on when to use this tool vs alternatives such as list_files or list_iceberg_tables. No context on prerequisites or typical use cases.

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