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

Annotations already establish readOnlyHint=true, destructiveHint=false and openWorldHint=true, so the safety profile is settled. The description adds genuinely useful behavior beyond that: prices are live BTC/NEAR valuations and each loan carries an actionable state (borrower repay, lender claim once overdue, pending extension). It says nothing about cost, latency, or how many loans a full sweep covers for a zero-argument global 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?

A single front-loaded sentence with a colon introducing the returned fields, then one supporting clause on intended caller. Every phrase carries information — the parenthetical enumeration of action states is dense, not padding.

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 and no parameters, the description carries the full burden of describing what comes back, and it does so: due date, hours remaining, live-price LTV, and per-loan permitted actions. An agent can decide to call this and know how to interpret the result without further documentation.

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 no parameters, so there is no parameter semantics to convey and the baseline of 4 applies. The description correctly gives no pseudo-parameter guidance that could mislead an agent into passing arguments.

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?

Specific verb and scope: "Watch every funded Pusaka loan at once" names the resource (funded loans) and the polled-monitoring nature, and the enumerated fields (due date, hours left, LTV, next actions) make the output concrete. It implicitly separates itself from offer-listing siblings via "funded," but never names an alternative explicitly, so differentiation is inferred rather than stated.

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?

"Built for an agent that lends or borrows on a schedule" gives a clear operating context — periodic polling by an agent with an active loan position. It also enumerates the follow-up decisions this feeds into (repay, claim collateral, accept an extension), which is strong forward guidance. It stops short of stating exclusions, e.g. that unfunded offers live elsewhere.

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