changedetection_get_snapshot

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

Annotations already declare readOnlyHint=true, destructiveHint=false, and openWorldHint=true, so the safety profile is covered. The description adds the endpoint and the 'latest' timestamp shortcut, but says nothing about what happens when the timestamp is not in history or what the response looks like for html vs non-html requests.

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?

Three short fragments, front-loaded with the action and endpoint. It is telegraphic rather than polished prose, but nothing is padded.

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?

A simple read-only tool with a fully documented schema and safety annotations needs less, but the description still leaves gaps for an agent: the return shape when html=true vs false, behavior for a missing timestamp, and the omitted 'previous' value are all unaddressed.

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 100%, so the baseline is 3. The description's note that timestamp accepts unix time or 'latest' largely restates the schema and actually omits the 'previous' value the schema allows, so it adds no meaningful semantics.

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 ('Fetch one snapshot') and pins it to the exact endpoint path, so the agent knows precisely what operation this is. It does not explicitly distinguish itself from close siblings like changedetection_get_diff or changedetection_list_history, which keeps it below a 5.

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?

There is no explicit when-to-use guidance and no named alternatives, so the agent must infer from the singular 'one snapshot' phrasing that list_history is for enumeration and get_diff is for comparisons. Usage is implied but never stated.

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