webdav_read_multiple_files

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

With no annotations provided, the description carries full burden for behavioral disclosure. While 'Read' implies a read-only operation, it doesn't specify authentication requirements, rate limits, error handling, or what happens when some files are inaccessible. For a batch operation on a remote file system, this leaves significant behavioral questions unanswered about partial successes, ordering guarantees, or performance implications.

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 a single, efficient sentence that communicates the core functionality without unnecessary words. It's front-loaded with the essential action and scope, making it immediately understandable. Every word earns its place in conveying the batch reading capability.

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 batch file reading operation with no annotations and no output schema, the description is insufficient. It doesn't explain return format (array of contents? success/failure status per file?), error handling for partial failures, or performance considerations for simultaneous reading. Given the complexity of batch operations and lack of structured metadata, more contextual information would be valuable.

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 description mentions 'multiple files' which aligns with the 'paths' parameter being an array, but adds no semantic detail beyond what the schema already provides. With 100% schema description coverage (the 'paths' parameter is well-described), the description doesn't enhance understanding of path formats, relative vs absolute paths, or file system constraints. Baseline 3 is appropriate when schema documentation is complete.

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 the verb ('Read') and resource ('contents of multiple files'), making the purpose immediately understandable. It distinguishes from single-file read operations by specifying 'multiple files simultaneously', though it doesn't explicitly differentiate from all sibling tools like 'webdav_get_remote_file' or 'webdav_read_remote_file' which appear to be single-file variants.

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 description provides no guidance on when to use this tool versus alternatives. With sibling tools like 'webdav_get_remote_file' and 'webdav_read_remote_file' that appear to handle single files, there's no indication whether this tool is preferred for batch operations or has different performance characteristics. No prerequisites, limitations, or comparison context is provided.

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