tenki_get_snapshot

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

Annotations already declare readOnlyHint=true, idempotentHint=true, and destructiveHint=false, so the safety profile is covered. The description adds that the tool returns status and metadata, but does not describe error behavior, authorization needs, or return structure beyond that.

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 short sentence with no filler. The subject, object, and selection criterion are all front-loaded, making the description immediately scannable.

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-only get-by-ID tool with only one required parameter and strong annotations, the description covers the essential invocation context. It names the return content (status and metadata), though it omits details like not-found behavior or whether the result is wrapped in a response 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 coverage is 0%, but the single parameter snapshot_id is semantically self-explanatory and the description reinforces that this ID selects the snapshot. It does not add format guidance or explain how to obtain a valid snapshot_id, though the minimal schema makes this a modest gap.

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 ('Fetch') and resource ('one snapshot's status and metadata') with an explicit identifier criterion ('by ID'). This clearly distinguishes it from list-style tools like tenki_list_snapshots and from tenki_get_snapshot_download_url.

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 use case is reasonably implied: call this when you have a specific snapshot_id and need that snapshot's status/metadata. However, it does not explicitly state when not to use it or mention alternatives such as list_snapshots or get_snapshot_download_url.

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