list_machine_manuals

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

No annotations were provided, so description carries full burden. It explains the tool reads a directory listing, returns structured data, and implies no side effects. The behavioral traits (read-only, local file access) are clearly communicated.

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 extremely concise: three short sentences covering purpose, usage, and return value. It is front-loaded and contains no filler.

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 zero parameters and an output schema described in the description (list of dicts with fields), the description fully covers what an agent needs. It is complete for its simple function.

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?

There are zero parameters, so baseline is 4 per guidelines. Description adds no parameter info (none needed), and schema coverage is 100% trivially.

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 clearly states it lists all machine manuals in a specific directory (resources/machine_manuals/) with file types PDF/TXT. It distinguishes itself from sibling tools like read_manual_excerpt by positioning itself as a preparatory step.

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?

It explicitly advises using this tool before read_manual_excerpt and extract_manual_specs, and instructs to pass filenames exactly as returned. This provides concrete usage guidance.

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