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

With readOnlyHint=true and destructiveHint=false, annotations already cover safety, and the description adds substantial behavioral context: one round-trip, cat -n style output, diagnostics behavior depending on VM warmth, include_references semantics, and the output cap with omitted files listed by name. No contradiction with annotations.

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 dense but every sentence earns its place, with the core purpose and benefit front-loaded. It efficiently packs usage examples, parameter meanings, return format, diagnostics options, and failure behavior without fluff.

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?

There is no output schema, so the description properly explains return behavior: header-per-file cat -n output, appended type errors, reference information, and output-cap behavior. The only small gaps are the exact meaning of the 'limit' parameter and the default 'auto' diagnostics mode, which are inferable but not fully explicit.

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 0%, so the description carries the full burden. It explains paths ('same item scheme as read_file', /_cdn/<name> support), diagnostics values ('off' to skip, 'wait' to force), include_references, and the 20-path limit. It does not explicitly describe the 'auto' value or the exact behavior of the limit parameter, leaving minor gaps.

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 states a specific verb and resource: 'Read MULTIPLE files from a Floot project in ONE call.' It clearly differentiates from the sibling read_file by emphasizing multi-file batching and cost savings, so an agent can immediately tell what this tool is for.

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 gives explicit when-to-use guidance: 'Prefer this whenever you need several files together' with concrete examples like an endpoint plus its schema and the hook that calls it. It also implies when individual reads are appropriate by noting that oversized batches should have files 'read individually.'

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