list_files

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

No annotations are provided, so the description must carry the behavioral disclosure burden. It clearly communicates a read-only enumeration scoped to a specific commit, which is useful, but it omits details such as return format, whether listing is recursive, or behavior on invalid commit IDs. This leaves some behavioral ambiguity for the agent.

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?

Two sentences with no filler. The core action is front-loaded in the first sentence, and the second sentence adds actionable usage guidance. Every element earns its place.

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 low-complexity list tool with two clearly documented parameters, the description covers what it does and when to use it. The main gap is the absence of any statement about output format (e.g., file names vs. paths), which would make interpreting the result slightly less certain.

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 description coverage is 100%, so both workspace_id and commit_id are already fully documented in the schema. The description reinforces the 'specific commit' scoping but adds no new parameter-level detail beyond what the schema provides, so the 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 a specific verb 'List' with a clearly defined resource: 'files present in a LinkML workspace at a specific commit.' This distinguishes it from sibling tools like read_schema, and the additional note 'Use this before targeting imported local schema files' clarifies its role in the workflow.

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 sentence 'Use this before targeting imported local schema files' provides a concrete, actionable scenario for when to invoke this tool. However, it does not explicitly name alternative tools or state when not to use it, so it falls short of fully explicit routing.

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