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

Annotations already declare readOnlyHint=true, idempotentHint=true, and destructiveHint=false, so safety is covered. The description adds nothing beyond noting that describe_operation exposes native request schemas, and says nothing about whether snapshots are point-in-time historical records, ordering, or pagination behavior.

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?

Two sentences, one of which is a verbatim duplicate of the other, and the non-duplicated sentence is a pointer to another tool. There is no wasted verbosity in the usual sense, but the content is under-specified rather than concise.

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?

No output schema, nested query object, 0% parameter coverage, and a completely opaque name — yet the description supplies none of the missing context. An agent cannot tell what it will receive or how to shape the query object.

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 0% and the tool has two parameters, including a free-form 'query' object with additionalProperties that is completely unspecified. The description does not mention leaseId, the query object, or any filtering capability, so it provides zero meaning beyond the schema.

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 only repeats the raw HTTP route 'GET /api/lease-determination/:leaseId/snapshots' twice, which effectively restates the tool title. An agent can infer it retrieves snapshots for a lease, but there is no plain-language statement of what a 'lease determination snapshot' is or what the response contains.

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?

No when-to-use guidance, no distinction from the sibling 'get_lease_determination_by_leaseId_7c3a36b7647aacec41762d2f' (the non-snapshot variant) or from 'describe_operation'/'execute_read'. The only actionable sentence points at describe_operation for schemas, not at when this tool applies.

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