iyke_lock_status

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

No annotations provided, so description carries full burden. It discloses that only active leases are considered and mentions return behavior for expired leases. However, it doesn't specify whether the operation is read-only or has side effects (though implied read-only). Could add more about permission requirements or rate limits.

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, no fluff. But missing parameter documentation makes it less concise in utility. One sentence could be moved to clarify parameters.

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?

No output schema, but description explains the held field. Lacks parameter details and does not fully define 'locked' in context of leases. For a simple check tool, it's moderately complete but not self-sufficient.

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 has 2 parameters (scope, resource) with 0% schema description coverage, but the description does not explain either parameter. Agent receives no guidance on what values to supply for 'scope' or 'resource'. This is a critical gap.

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 clearly states the tool checks lock status on a resource, specifying it considers only active leases and explains the return value meaning ('held=false if expired'). Distinguishes from siblings like iyke_lock_acquire.

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?

Purpose implies use before acquiring/releasing locks, but no explicit guidance on when to use vs alternatives (e.g., iyke_lock_release). No exclusion criteria or prerequisites mentioned.

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