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

Annotations already declare readOnlyHint=true and destructiveHint=false, covering the safety profile. The description adds no further behavioral detail such as pagination, rate limits, or return format. It neither contradicts the annotations nor enriches them, so a neutral score 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?

One compact sentence with no extraneous words. The verb and resource are front-loaded, making the tool's purpose immediately clear. 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?

For a read-only batch fetch with optional parameters and no output schema, the description is minimally adequate. It does not explain id formatting, request limits, or response shape, but given the annotations cover safety and the schema documents the parameters, it meets a basic threshold without being rich.

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% for both parameters (ids and params), so the baseline is 3. The description does not add beyond the schema—it merely repeats that deposits are fetched and does not clarify formatting or usage nuances, such as how ids are delimited.

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 ('fetch'), resource ('multiple deposits'), and source ('ProtocolViewer'), which clearly distinguishes it from the singular peer_pv_deposit_show and the non-PV peer_deposit_show_many. The purpose is unambiguous and the verb-resource pairing is specific.

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 'directly from ProtocolViewer' implies this is the direct-path variant, but the description does not explicitly name alternatives (e.g., peer_deposit_show_many) or provide when-to-use/when-not-to-use conditions. Context is present but exclusion and comparative guidance are absent.

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