dbfs_get

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

The disclosure of base64-encoded output adds value beyond the readOnlyHint annotation. However, it does not mention file size limits or error behavior.

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?

A single, front-loaded sentence that is entirely non-redundant and efficient.

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?

Lacks details on optional parameter behavior (e.g., default to whole file) and error conditions, though output schema existence reduces the need for return value description.

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?

With only 33% schema coverage, the description fails to explain offset and length parameters. Only 'path' is obvious; the optional parameters have no semantic guidance.

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 'Read bytes from a DBFS file' with a specific verb and resource, and distinguishes from siblings like dbfs_put (write) and dbfs_get_status (metadata).

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?

No explicit when or when-not guidance is provided. While the purpose is clear, there is no discussion of alternatives or when to use offset/length parameters.

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