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

Annotations already declare readOnlyHint=true, destructiveHint=false, and openWorldHint=true, so the safety profile is covered structurally. The description adds that the listing is unfiltered ('every Pusaka') and includes an aggregate summary of open loan offers and their escrowed NEAR, which is useful behavioral context. It says nothing about ordering, result size, or pagination for what could be an unbounded list.

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 dense sentence with the core output fields front-loaded and the aggregate loan-offer detail following the semicolon. Every clause corresponds to real returned data, though the run-on structure makes it slightly harder to scan than a short bulleted enumeration would be.

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?

There is no output schema, so the description must carry the return shape, and it does so by naming each field plus the loan-offer aggregates. For a parameterless read-only listing tool this is close to sufficient; the only gap is the absence of any note on result volume or ordering.

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 baseline is 4. The description correctly implies no input is needed and instead spends its words describing what comes back, which is the right emphasis for a parameterless tool.

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 ('List') and resource ('every Pusaka') and enumerates the returned fields: owner, BTC verified on NEAR, sale price, loan status, plus open loan-offer counts and escrowed NEAR. An agent knows exactly what this tool yields, but there is no explicit differentiation from siblings such as pusaka_inspect or pusaka_portfolio, so it stops short of a 5.

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 when-to-use guidance, no prerequisites, and no mention of alternatives. The word 'every' implies an unfiltered bulk listing, which hints at a use case, but the agent must infer when to prefer this over pusaka_inspect or pusaka_market_book.

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