Get ZK Checkpoint

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

Annotations already indicate this is a read-only, idempotent, non-destructive operation with open-world semantics. The description adds context by specifying what data is returned ('proof data and state roots'), which is valuable beyond annotations. It does not mention rate limits or authentication needs, but annotations cover the core safety profile adequately.

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, efficient sentence that front-loads the core purpose and includes essential details without any wasted words. Every part of the sentence contributes to understanding the tool's function.

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's simplicity (one parameter, read-only operation with good annotations), the description is largely complete. However, without an output schema, it could benefit from more detail on return format (e.g., structure of proof data). The annotations and schema cover safety and inputs well, but the output aspect is lightly addressed.

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%, with the single parameter 'checkpoint_id' documented as 'Resource ID'. The description does not add further details about parameter format or semantics beyond what the schema provides, so the baseline score of 3 is appropriate.

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 clearly states the specific action ('Get') and resource ('ZK-rollup checkpoint'), including what data is retrieved ('proof data and state roots'). It distinguishes from sibling tools like 'dual_list_checkpoints' by specifying retrieval of a single checkpoint rather than listing multiple.

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 implies usage when a specific checkpoint ID is known, but does not explicitly state when to use this tool versus alternatives like 'dual_list_checkpoints' for browsing or other get tools for different resources. No explicit exclusions or prerequisites are mentioned.

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