spraay_escrow_get

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

Annotations already declare readOnlyHint=true and openWorldHint=true, but the description adds valuable context: data persists in Supabase and there is a cost of $0.001 USDC. These details inform the agent about external dependencies and cost implications beyond what annotations provide. No contradiction with annotations.

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 consists of two concise sentences: first sentence states the core purpose with specific details, second sentence adds essential behavioral context (persistence and cost). No unnecessary words, front-loaded with the main action.

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?

The description covers the tool's purpose, key return fields, data source, and cost. Since an output schema exists, return format details are not needed. It does not explicitly mention authentication requirements, but that is likely implied by the broader system. Overall complete for a read-only single-ID lookup tool.

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 input schema has 100% description coverage for its single parameter, so the schema already documents the ID field adequately. The description reiterates 'by ID' but adds no new semantic meaning beyond what the schema provides. Baseline of 3 is appropriate.

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 ('Get') and resource ('escrow details'), lists key fields (status, participants, conditions, balance, timestamps) and explicitly mentions the lookup by ID. This clearly distinguishes it from sibling tools like spraay_escrow_list (which likely lists all escrows) or spraay_escrow_create.

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 usage when you have an escrow ID and need full details, but it does not explicitly state when to use this tool over alternatives like spraay_escrow_list, nor does it provide conditions for when not to use it. No sibling tools are referenced.

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