lock_lock_try

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

Discloses non-blocking behavior and return structure ({acquired, held_by?}), but lacks details on reentrancy, lock scope, or automatic release. No annotations provided, so description carries full burden.

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?

Single sentence with no wasted words. Prefixed '[lock]' helps categorize. Could benefit from slight expansion on 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?

Very brief for a lock tool with 3 parameters and output schema. Does not explain TTL, owner usage, or whether lock is distributed/global. Output schema exists but content not in description.

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?

Input schema has 3 parameters (name, owner, ttl_s) with 0% schema description coverage. Description mentions none of them, adding no value beyond the raw 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?

Clear verb+resource: 'Non-blocking lock attempt' and distinguishes from sibling lock_lock_acquire by specifying 'non-blocking' and 'returns immediately'.

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?

Implies use for non-blocking attempts but does not explicitly contrast with lock_lock_acquire (which may block) or other siblings like lock_lock_release. No alternative scenarios or exclusions given.

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