get_task_escrow_status

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

With no annotations provided, the description carries the burden of explaining behavior. It conveys that the operation is a read ('Retrieves') and includes the price note, but it does not explicitly state that the operation has no side effects or what happens for invalid or missing escrow IDs.

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 concise and front-loaded with the free cost and primary behavior. The Args section adds a little structure, but there is minimal fluff or redundant content.

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 simple single-parameter read tool, the description covers the essential return contents and the input. It lacks error-condition details on missing escrows, but those are less critical given the low complexity and explicit state enumeration.

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%, so the description must compensate for the parameter. It merely restates that escrow_id is 'ID of the escrow to inspect,' adding little beyond the schema's existing 'Escrow Id' title and string type. No format, origin, or validation context is provided.

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 uses a specific verb ('Retrieves') and resource ('task bounty escrow'), and enumerates the returned fields (state, worker ID, attestation receipt). It is clearly distinguishable from mutating siblings such as create_task_bounty_escrow or release_task_bounty.

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 implies this is the read/status tool for escrows, but it never explicitly states when to use it versus alternative lifecycle tools. There is no mention of exclusions or when not to use it, so guidance is only implicit.

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