get_lock_status

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

No annotations are provided, but the description indicates a read-only operation ('Check the current status'). It does not mention any side effects, permissions, or rate limits, which is acceptable for a simple status check.

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 well-structured sentences. The first explains the tool's action and resource, and the second provides a concrete use case. No unnecessary 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?

While the description lacks details on the output format (e.g., whether it returns a boolean, text, or object), it is sufficient for a no-parameter status check tool. It contextualizes the two lock types and their durations.

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 tool has no parameters, and the schema coverage is 100% (empty). The description adds value by explaining what the status query covers (both lock periods), which goes beyond the empty 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 specifies the tool checks the status of two distinct lock periods (weekly Arbitrum deposit lock and 24h Hyperliquid withdrawal lock). It differentiates from sibling tools like 'get_vault_status' and 'get_pending_deposit' by focusing specifically on lock periods.

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 explicitly states when to use the tool: 'when a user asks why they cannot deposit or withdraw right now.' It lacks explicit when-not-to scenarios or alternatives, but the usage context is clearly defined.

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