snapshot_custom_variables

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

No annotations are provided, so the description bears full responsibility for disclosing behavior. It states a read operation but does not confirm it is read-only or whether it has any side effects. It lacks information on permissions, rate limits, or intended use scenarios.

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 sentence, concise and without extraneous words. However, it could be rephrased to front-load the key action and resource more clearly. It is acceptable in terms of brevity.

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?

Given the tool has a simple input schema (one parameter) and an output schema exists, the description could be more complete. It fails to explain what a 'snapshot payload' is or how the output is structured. While the output schema may clarify return values, the description leaves ambiguity about the tool's purpose.

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%, meaning the description adds no meaning to the parameter 'names_json'. It does not specify the expected format (e.g., JSON array, comma-separated list) or how to pass multiple variable names. The schema alone provides a title but no semantic 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 the verb 'Read' and identifies the resource as 'custom variables' and the action as creating a 'snapshot payload'. This distinguishes it from sibling tools like get_custom_variable (reads a single variable) and snapshot_page_inventory (snapshots a page). However, the phrase 'snapshot payload' is somewhat vague.

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 provides no guidance on when to use this tool versus alternatives. It does not mention prerequisites, when not to use, or compare with sibling tools like get_custom_variable or snapshot_page_inventory.

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