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

Annotations already declare readOnly, idempotent, non-destructive and closed-world, so the safety profile is covered. The description adds real value beyond that by enumerating the aggregate fields returned, which is the main behavioral question for a summary tool with no output schema.

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 sentence, front-loaded with the scope (tokenized treasury market) followed by the returned metrics. No filler and nothing to trim.

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 parameterless read-only summary with no output schema, listing the returned fields is what the agent needs. The only residual gap is the boundary with sibling summaries — 'other tokenized real-world assets' could overlap with the separately exposed tokenized equity summary, which is left unresolved.

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 nothing to document and no ambiguity for the caller. Baseline 4 applies.

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 (tokenized treasury market) and enumerates exactly what the tool returns: distinct tokens, total TVL, median APY, top tokens by TVL, plus other tokenized RWA totals. That is enough to distinguish it from list-style siblings such as list_rwa_yields, though it never names a sibling 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?

Usage is only implied: an agent can infer this is the aggregate/summary entry point versus the list_* detail tools. There is no explicit when-to-use or when-not-to-use statement, and no guidance on how it relates to tokenized_equity_summary or stablecoin_yield_summary.

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