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

Annotations already declare readOnlyHint=true and destructiveHint=false, so the read-only safety profile is covered. The description adds the 'daily' frequency but does not disclose output structure, date range behavior, pagination, or any other beyond-schema behavioral traits.

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, front-loaded sentence with no filler or redundant content. It communicates the core operation efficiently.

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?

There is no output schema, sibling-routing guidance, or explanation of what constitutes a snapshot, leaving the agent to guess at expected results and appropriate usage. The open-ended params/options objects further compound the ambiguity.

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 parameters already have meaningful descriptions like 'Vault identifier' and 'Snapshot options.' The tool description only restates the resource and does not deepen understanding of how parameters interact or affect the snapshots returned.

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 names a specific action ('Fetch'), a concrete resource ('daily snapshots'), and a target ('a vault'), so an agent can tell this is a read operation for historical vault snapshot data. It does not fully explain what a 'snapshot' is or how it differs from other vault-related tools, leaving some ambiguity.

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 provides no guidance on when to use this tool instead of siblings like peer_vault_show or peer_indexer_deposits_snapshots. No alternatives, exclusions, or context scenarios are mentioned, which is a notable gap given the large sibling tool list.

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