lock_lock_status

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

The description discloses the return format {held, owner?, remaining_s?}, which is a non-destructive read operation. No side effects are implied. With no annotations, it provides adequate behavioral transparency.

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: one sentence with no wasted words. It front-loades the purpose and return type clearly.

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 one parameter and an output schema that describes the return, the description is complete. It tells what the tool does and what it returns, covering all necessary information.

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 single parameter 'name' is self-explanatory as the lock name. The description adds no extra meaning beyond the schema, but schema coverage is 0% and the param is straightforward. 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 verb 'Check' and the resource 'if lock is held', which is specific and distinguishes this tool from sibling tools like lock_acquire, lock_release, etc.

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 for checking lock status but lacks explicit guidance on when to use it versus alternatives like lock_stats or lock_list. It does not mention when not to use it.

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