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

Annotations already declare readOnlyHint=true, destructiveHint=false, openWorldHint=true, so the safety profile is covered. The description adds value by disclosing the returned dimensions, including that Bitcoin values come in both sats and USD, and that the call is scoped to this agent's account by default. No pagination or ordering behavior is mentioned, keeping it from a 5.

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?

One front-loaded sentence naming the scope, followed by a compact enumeration of the six returned data categories and a default-behavior clause. Nothing is repeated from the name or the annotations; every clause adds information.

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 carries the return-value burden, and it does so by listing all data categories and the dual-unit Bitcoin values. With only one optional parameter the tool is simple enough that the remaining gaps - unknown-account behavior and result shape details - are minor.

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 single account_id parameter has 0% schema description coverage, so the description must compensate - and it does by stating that the account defaults to this agent's account, which the schema does not express. It still doesn't clarify what form account_id takes or what happens with an unknown account.

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?

States the resource precisely: 'Everything one NEAR account has in Pusaka', then enumerates the contents (held Pusakas, proven Bitcoin in sats and USD, loans owed and funded, escrowed offers, heir designations). An agent knows exactly what aggregate view it gets. It stops short of a 5 because it never distinguishes itself from nearby aggregates like pusaka_overview or pusaka_credit_record.

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?

'Defaults to this agent's account' implies the common self-lookup case, so usage is inferable. However, there is no explicit statement of when to choose this over pusaka_overview, pusaka_credit_record, or pusaka_deals, and no exclusions or prerequisites.

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