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

Annotations already declare readOnlyHint/openWorldHint, so the safety profile is covered. The description goes further with substantive epistemic caveats: escrow objects are ledger-verified while the treasury role is only an owner-confirmed declaration, and an escrow does not establish who controls the destination after release. That is real behavioral context an agent could otherwise over-assume. It stops short of noting freshness/pagination behavior for an openWorld read.

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 sentences, front-loaded with the returned payload and followed by the caveat; nothing is wasted. The first sentence is dense and slightly run-on, but every clause carries information an agent needs.

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?

With no output schema, the description carries the full burden of explaining the return value, and it does so field by field (amount, destination, finish-after, cancel-after, locked/releasable/expired state, total escrowed, next unlock) plus the interpretive limits. Nothing an agent needs to call and read it correctly is missing.

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 takes zero parameters, so the schema-side burden is nil and the baseline is 4. The description correctly adds no parameter discussion, which 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 gives a specific verb+resource ('Ledger-indexed schedule of ... treasury ASTEROID escrows') and enumerates what each escrow object contains, so the agent knows this returns per-escrow detail. It does not explicitly contrast itself with the nearby get_escrow_stats, leaving the schedule-vs-aggregate boundary to inference rather than stating it.

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?

There is no statement of when to reach for this tool versus get_escrow_stats or the verification tools, and no prerequisites or exclusions are given. The agent must infer usage from the noun 'schedule' alone.

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