create_checkpoint

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

The description does not contradict annotations (destructiveHint=false). It adds 'rollback point' context but does not disclose other behavioral traits such as whether an existing checkpoint with the same label is overwritten, permission requirements, or error handling. Annotations already indicate non-destructive nature.

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 extremely concise with no unnecessary words. It front-loads the core purpose and follows with a clear parameter list. Every sentence is meaningful.

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 3 parameters, no enums, and an output schema exists, the description covers the essentials. It could mention the return value or error scenarios, but the presence of an output schema reduces the need. Adequate for a simple create operation.

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 description adds meaning beyond schema titles: it clarifies 'mission_id: Mission to checkpoint', 'label: Human-readable label', and 'metadata: JSON string of additional metadata' (the schema allows both string and object but description specifies JSON string). This compensates for the 0% schema coverage.

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 action ('Create a checkpoint') and the resource ('for a mission') with explicit mention of 'rollback point'. It distinguishes well from siblings like 'get_checkpoint', 'list_checkpoints', 'rollback_to_checkpoint'.

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 the usage context (creating a rollback point) but does not explicitly state when to use vs. alternatives like 'create_mission' or 'rollback'. It provides clear context but lacks exclusion or alternative guidance.

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