List KiCad Checkpoints

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

With no annotations provided, the description must carry the burden of behavioral disclosure. It states that it lists checkpoints, which indicates a read-only operation, but does not disclose details such as pagination behavior, sorting, or what happens if the path is invalid. It adds the context that it's specific to KiCad Copilot, but lacks depth.

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 very concise: one sentence clearly stating purpose. The reference to agent instructions adds a bit of overhead but is harmless. It is front-loaded with the key action and resource.

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 no output schema and no annotations, the description does not explain what the response looks like or how pagination works. The tool is relatively simple (list operation), but with three parameters and no return information, the description is incomplete for an agent to fully understand the outcome.

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?

The schema description coverage is 100%, so all parameters (path, page, limit) have descriptions in the schema. The description does not add extra meaning beyond the schema, but since the schema is thorough, a baseline 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 states 'List file checkpoints saved by KiCad Copilot', which clearly identifies the action (list) and resource (file checkpoints), and names the source ('KiCad Copilot'). It does not explicitly distinguish itself from sibling tools like save_checkpoint or restore_checkpoint, but the verb 'list' and resource 'checkpoints' make the purpose clear enough.

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 guidance about when to use this tool versus alternatives. The description only mentions the purpose and refers to an agent instructions file, which is not accessible to the model. No exclusions or alternative tool references are provided.

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