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

Annotations already declare readOnlyHint=true, idempotentHint=true, and destructiveHint=false. The description restates 'Side effects: none (read-only)' and adds the return format ('base64 TIFF page in structured output'), which adds some value. However, most behavioral safety context is already in the annotations, and the return format is likely covered by the existing output schema.

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 short and front-loaded with the core purpose. The side-effects sentence is slightly redundant with the annotations, but it does not hurt. Overall it is efficient and easy to consume.

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 strong annotations, complete input schema, and presence of an output schema, the description is sufficient for a simple read-only tool. It could improve by explicitly naming sibling tools for full-file or thumbnail downloads, but it is not critically incomplete.

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 coverage is 100%, so all three parameters are already documented. The description does not add parameter-specific meaning beyond what the schema provides, such as clarifying fax_id or user_id semantics or page_num bounds.

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 ('Download'), a specific resource ('single page from a fax file'), and the format ('TIFF'). It clearly distinguishes this tool from siblings like get-file (whole file) and get-fax-thumbnail (thumbnail) by focusing on a single page.

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 implies usage when a single page is needed, but it does not explicitly contrast with alternatives such as get-file or get-fax-thumbnail, nor does it state when not to use this tool. The usage context is clear but relies on inference rather than explicit guidance.

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