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

With no annotations, the description carries the full burden. It discloses two key behaviors: the 60-minute lock duration and the exclusivity (one holder at a time). However, it omits critical details like contention behavior (blocking vs. error), release mechanism, and whether the lock is per user or global. It adds some value but leaves significant gaps.

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—two short sentences. The core behavior is front-loaded. While it is efficient, the brevity contributes to the lack of contextual detail, but as a structural score it is well-organized and wastes no words.

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 lock-acquisition tool with 4 parameters and no output schema, the description is incomplete. It does not explain the parameters, the consequences of claiming (how to release, what happens on timeout), or how to handle conflicts. An agent would need to infer too much to use this correctly.

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 only 25% (only 'ticket' has a description). The description adds no meaning for the parameters beyond noting that 'job' is required. It does not explain the roles of 'key', 'name', or 'ticket', nor how they relate to claiming. The description fails to compensate for the sparse schema.

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 a specific action: 'Takes the lock on a job for 60 minutes.' It identifies the resource (a job) and the key constraint (one holder at a time). It does not explicitly distinguish from siblings like name_claim, but the resource differs enough that the purpose is unambiguous.

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 guidance on when to use this tool versus alternatives. It only mentions 'job required' without explaining the intended workflow, such as when claiming is appropriate or what to do if the lock is already held. There is no mention of alternatives or exclusions.

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