Lock Checkpoint

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

Description reveals the state-changing action (locks the checkpoint) but does not disclose side effects such as whether it requires an already loaded checkpoint, or if it errors when already locked, or response formats. No annotations are available, so none not required. Does not contradict annotations.

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?

One sentence only, with endpoint embedded, no filler or redundant wording.

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?

For a zero-parameter lock operation with no output schema, the description sufficiently names the endpoint and impact. However, lacks input on what response or trigger conditions, but these are not critical for such a simple low-parameter tool.

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?

No parameters are defined; schema coverage is 100% and the default value baseline assigned as there are no parameters to specify.

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?

Description uses a specific verb ('Prevent') with a specific resource ('current checkpoint') and cites the HTTP endpoint (POST /sdapi/v1/lock-checkpoint). It clearly distinguishes from sibling tools by specifying the lock (prevent unload) goal.

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?

No explicit guidance on when to use this tool vs alternatives (e.g., unload, reload, or select checkpoint). It only describes the action, not a context or exclusion, so the agent must infer usage.

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