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

Annotations already declare readOnlyHint, idempotentHint and non-destructive, so the safety profile is covered. The description adds genuinely non-structured context about the returned data — amounts are bare numbers without currency — which prevents misinterpretation. It says nothing about pagination or error behavior, but this is a single-item getter where that matters less.

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 short sentences, front-loaded with the core action and followed by the one caveat that actually matters. Every clause earns its place with no filler.

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, the description carries the burden of return-value semantics, and it does flag the key gotcha (unitless amounts and where to resolve currency). The remaining gap is any indication of what fields a snapshot contains, but for a one-parameter getter this is close to sufficient.

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% and the single 'id' parameter is fully documented as a UUID. The description's 'by ID' adds no syntax or format detail beyond what the schema already states, so the baseline of 3 applies.

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?

States a specific verb and resource ('Get a single dashboard snapshot by ID') that an agent can map directly onto the tool. It does not, however, distinguish itself from close siblings such as get_dashboard_summary or list_dashboard_snapshots, so the agent must infer the difference from names alone.

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 explicit condition is given for choosing this tool over get_dashboard_summary or list_dashboard_snapshots. It does supply useful downstream guidance ('call get_organization_settings for currency_code'), which is implied usage context rather than a selection rule.

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