webdav_read_remote_file

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

With no annotations provided, the description carries the full burden of behavioral disclosure. It mentions 'enhanced options' but does not explain what 'read content' entails (e.g., text/binary handling, encoding, error behavior, or authentication requirements). This leaves critical behavioral traits unspecified for a file-reading operation.

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 front-loads the core purpose and includes key details. Every word earns its place, with no redundancy or unnecessary elaboration, making it highly concise and well-structured.

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 complexity of file reading with options, no annotations, no output schema, and partial parameter coverage, the description is insufficient. It lacks details on return values, error handling, authentication, and how the tool differs from siblings, making it incomplete for effective agent 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?

The schema description coverage is 67% (2 out of 3 parameters have descriptions), and the description adds minimal value by referencing 'head/tail' without explaining their interaction or default behaviors. It does not clarify if 'head' and 'tail' are mutually exclusive or how they work with the 'path' parameter, so it meets the baseline but does not compensate for the partial schema coverage.

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 action ('Read content from a file') and resource ('on a remote WebDAV server'), with the enhanced options ('head/tail') providing additional specificity. It distinguishes itself from the sibling 'webdav_get_remote_file' by emphasizing the head/tail functionality, though the distinction could be more explicit.

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 like 'webdav_get_remote_file' or 'webdav_range_request'. It mentions enhanced options but does not specify scenarios where head/tail are preferred over other reading methods, leaving usage context unclear.

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