list_recordings

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

States 'Does not require loading,' implying safe, non-destructive operation. With no annotations, this is valuable context. Describes return type (file information) but could mention permissions or scalability (e.g., large directories).

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?

Three sentences, each serving a purpose: purpose+output, when to use, path parameter detail. No fluff, front-loaded with key information.

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?

Output schema exists but is not shown; description provides a high-level overview and one parameter detail. Missing explanations for two parameters (after, before) that are not in schema descriptions. Adequate for basic understanding but incomplete for full use.

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 0%, so description must compensate. Only 'path' parameter is explained (absolute directory). 'after' and 'before' parameters are not described at all; their purpose and format remain unclear. This is a significant gap.

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 it discovers MCAP recording files, lists their metadata (names, sizes, durations, etc.), and does not require loading. It distinguishes from sibling tools like load_recording by explicitly noting it's a discovery 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?

Explicitly advises to 'Use this first to see what data is available before loading.' Provides context on default project directory scanning and flexibility via absolute path. Lacks explicit exclusions but sufficient for typical use.

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