agentbus_lock_acquire

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

The description discloses that the lock is 'exclusive' and 'advisory', which partially informs behavior. However, with no annotations, it fails to detail important traits like blocking, timeout behavior, or error conditions on conflict.

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 a single, well-formed sentence with no redundancy. It is concise, though could benefit from a second sentence explaining usage.

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?

Despite having an output schema, the description does not explain return values or behavior like lock expiration, contention handling, or error states. For a locking tool, this is insufficient.

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 description coverage is 0% and the description includes no explanation of parameters (owner_id, resource, auth_token, ttl_seconds). Since the description must compensate for the lack of schema docs, it fails entirely.

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 'Acquire an exclusive advisory lease on a workspace resource' uses a specific verb ('acquire') and specific resource ('lease on a workspace resource'), clearly distinguishing it from siblings like release, renew, or status.

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 is provided on when to use this tool versus alternatives (e.g., when to acquire a lock vs. poll or status). The description lacks context about prerequisites, contention, or blocking behavior.

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