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

No annotations are provided, so the description carries the full disclosure burden. It is a zero-parameter read-only-sounding tool, and the description does reveal what is returned (doc links plus the current mainnet slot), but it says nothing about freshness, caching, or whether the slot value is live.

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 tight sentence with no filler, and the core content (backing and xAsset leverage) is front-loaded before the supplementary doc-links and slot clauses. Only minor polish would improve it.

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 annotations, the description gives an adequate picture of the returned content for a simple zero-param explanatory tool. It stops short of specifying scope limits or freshness, which is the only remaining gap.

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 there is no parameter semantics burden to compensate for; the baseline for a no-param tool is 4. The description correctly implies no inputs are needed.

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 a specific verb (Describe) applied to a specific resource (Hylo backing and xAsset leverage) and names the concrete payload additions (doc links, current mainnet slot). It is clearly differentiated from the sibling getters by being an explanatory rather than state-retrieval tool, though it never explicitly contrasts itself with them.

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?

Usage is implied: an agent can infer this is for conceptual/background explanation rather than fetching live protocol state. There is no explicit when-to-use, no when-not-to-use, and no pointer to an alternative sibling, so the routing guidance is only inferential.

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

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

With no annotations, the description carries the burden, and it does disclose one non-obvious trait: the NAV value is derived via an SDK formula rather than read directly on-chain. However, it says nothing about data freshness, RPC dependencies, or failure behavior, so the disclosure is partial.

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 read targets front-loaded before the derived NAV computation. No filler, though the semicolon-joined clauses make it slightly dense.

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?

No output schema exists, so the description must describe returns, and it names the three values (reserve, eHYUSD supply, NAV) but not their units, precision, or structure. Adequate for a zero-param read tool but leaves the return shape underspecified.

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 of 4 applies. The description correctly adds no parameter commentary, as there is nothing to disambiguate.

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 states a concrete verb+resource: reading the hyUSD Earn Pool reserve and eHYUSD supply, plus computing eHYUSD NAV. It is clearly narrower than get_protocol_state, though it never explicitly says how it differs from that sibling, so an agent must infer the boundary.

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 mention of when to prefer get_protocol_state or get_wallet_exposure instead, and no prerequisites. Usage is only implied by the read-only framing of the verb 'Read'.

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

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

With no annotations, the description must carry the behavioral burden; it does disclose meaningful traits — 'verified' data provenance, a point-in-time snapshot ('at one mainnet slot'), and explicit exclusions ('No inferred CR or price'). It still omits read-only declaration, auth/permission needs, and any rate or freshness caveats, so it is only partially transparent.

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 dense sentences, front-loaded with what is read before the exclusion note. Every clause carries information: resource list, snapshot scope, and the negative constraint.

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?

For a zero-parameter read tool with no output schema, the description usefully enumerates the data items returned (mint supplies, virtual stablecoin supply, pause flags) and what is not returned. It could say more about the return shape or units, but it is largely sufficient to call the tool correctly.

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 and schema coverage is 100%, so the baseline of 4 applies. There is nothing for the description to clarify beyond confirming the call needs no 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?

States a specific verb (Read) and enumerates the concrete resources returned: Hylo SPL mint supplies, SOL-pool virtual stablecoin supply, and pause flags. The scope is precise enough to separate it from get_earn_pool_state and get_wallet_exposure, though no sibling is named explicitly.

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 clause 'No inferred CR or price' implies the agent should not call this for collateral-ratio or price data, which is a mild when-not signal. However, no alternative tool is named and no positive condition for choosing this tool is given, so usage remains implied rather than explicit.

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

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

With no annotations, the description carries the burden: it discloses read-like behavior, direct-only balances, and a point-in-time mainnet slot. It omits read-only/side-effect confirmation, the slot-selection rule, and return format details.

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 no filler, naming the action, token set, scope, and address type efficiently.

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 tool is simple and the schema covers the lone wallet input, but with no output schema the description should clarify return shape and how the 'one mainnet slot' is chosen. These are meaningful gaps for an agent interpreting results.

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?

There is only one parameter, and the schema fully documents it as a base58 public Solana wallet address with no wallet connection required. The description adds 'any public address' but little semantic detail beyond the schema.

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 a specific verb ('Find') and resource ('direct SPL balances of hyUSD, xSOL and eHYUSD') scoped to a public address. This clearly distinguishes it from the protocol/pool-state siblings and explain_mechanism.

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 scope implies it is for direct wallet holdings rather than protocol or pool state, but it does not explicitly say when to choose it over get_earn_pool_state or explain_mechanism. No exclusions or alternatives are named.

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