bw_unlock

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

Describes the tool's behavior: releasing a lock, discarding changes, no activation. Specific DTP lock behavior mentioned (SM12: RSBKDTP). Without annotations, this is sufficient; could note that unsaved changes are lost, but 'discard changes' implies this.

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?

Two sentences: first states core purpose, second provides critical DTP-specific nuance. No wasted words, front-loaded.

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 simple tool with 2 parameters, no output schema, and no nested objects, the description covers the behavior, use case, and special cases (DTP lock). Complete.

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 100% with descriptions for both parameters. The tool description does not add further semantic meaning beyond the schema, so baseline score applies.

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?

Clearly states the action (release a lock without activating), the resource (BW object), and provides a typical use case (after aborted create/update). Distinguishes from siblings like bw_activate and bw_delete.

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?

Explicitly says when to use (to discard changes and free a lock) and gives a concrete example (aborted create/update). Also provides DTP-specific detail. Does not explicitly state when not to use, but context is clear for a simple operation.

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