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

Annotations already declare readOnlyHint=true and destructiveHint=false, so the safety profile is covered. The description adds only the domain context 'on Peerlytics' and provides no further behavioral detail such as response shape, pagination behavior, or behavior on invalid or missing deposit IDs.

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 a single concise sentence with no filler, which is structurally clean. However, it is so minimal that it provides little beyond the tool name and schema, bordering on under-specification rather than efficiently useful conciseness.

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 no output schema and many closely related sibling tools, the description is not complete enough for an agent to confidently invoke this tool correctly. It does not explain what 'looking up' returns, how this explorer view differs from other deposit tools, or how the parameters like offset and params affect the call.

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%, so the schema already documents id, limit, offset, and params. The description adds no additional parameter meaning, but per the baseline for high schema coverage, a 3 is appropriate.

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 clear verb ('look up') and resource ('deposit') in a named domain ('Peerlytics'), so an agent can tell this is a read/lookup operation. However, it does not distinguish this tool from many sibling tools with similar lookup semantics, such as peer_deposit_show, peer_indexer_deposits_show, or peer_market_explorer_search.

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 gives no guidance on when to use this tool versus alternatives. Given the large sibling list containing several deposit-related lookup tools, an agent has no explicit context for choosing this one, nor any exclusions or conditions.

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