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

Annotations already declare readOnlyHint, openWorldHint, idempotentHint, and destructiveHint, so the description adds value by disclosing the authorization requirement and the 'fresh' nature of the snapshot. These details go beyond the structured annotations and do not contradict them.

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, well-structured sentence that front-loads the core action and then adds the permission condition. There is no wasted wording, and all content earns its place.

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 simple read tool with one parameter and strong annotations, the description covers the key prerequisites (permissions) and the behavioral nuance (fresh snapshot). The return value is implied by 'snapshot,' and since no output schema exists, this is acceptable. The auth condition is a meaningful addition.

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?

With 0% schema description coverage, the description should compensate by explaining the parameter, but it does not mention collectionAddress at all. The parameter name is somewhat self-explanatory, but the description adds no additional meaning about its format or usage, leaving the agent to infer from the tool name and domain context.

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 uses a specific verb ('Read') and resource ('collection snapshot'), clearly indicating the tool's function. It also adds the context of a 'fresh' snapshot, which distinguishes it from cached reads. However, it does not explicitly contrast with sibling tools like list_collections or get_item, though the singular 'collection' implies a single-resource lookup.

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 states a clear prerequisite: use only when the authenticated wallet holds collection or parent rights. This is useful context but does not advise when to prefer this tool over alternatives or when not to use it. No specific alternative tools are mentioned, so the guidance is implied rather than explicit.

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