Read Remote File Base64

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

Annotations already declare readOnlyHint=true and openWorldHint=true, establishing this as a safe read operation. The description adds the intended use case (small binary files) and encoding (base64), which goes beyond annotations, but it doesn't disclose size limits, error behavior, or return format details. The added context is useful but limited, so a 3 is appropriate.

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 two short sentences with no redundant information. Every word adds value: 'Read a file from the configured SSH host as base64' defines the action, and 'Use this for small binary files' gives usage guidance. 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?

With 100% schema coverage and a read-only tool, the description is sufficiently complete for an agent to select and invoke it correctly. It doesn't explain return values (no output schema) but mentions base64 encoding. The 'small binary files' hint aligns with maxBytes constraints, though it doesn't specify the 20MB maximum explicitly. Minor gaps in error handling are acceptable given the simplicity.

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 100%, with all parameters (host, path, maxBytes, timeoutMs) individually documented. The description does not add meaning beyond the schema, such as clarifying parameter relationships or defaults. Baseline 3 is correct when schema handles parameter documentation.

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 a file from the configured SSH host as base64', specifying the verb (read), resource (file), and format (base64). It also distinguishes itself from sibling tools like remote_ssh_read_text (for text) and remote_ssh_write_file_base64 (for writing) by focusing on reading binary files.

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 phrase 'Use this for small binary files' provides clear context on when to use the tool, but it does not explicitly name alternatives or state when not to use it (e.g., for text or large files). Sibling tool names imply alternatives, but the description itself doesn't reference them, so it stops short of a 5.

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