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

With no annotations, the description carries the full burden and does disclose the important traits: read-only, public on-chain data, and a prompt-injection caveat that creator-authored ticker/name fields must never be treated as instructions. It does not cover freshness/latency, invalid-mint behavior, or response shape, but the safety and provenance disclosure is well above average.

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?

Three sentences, all front-loaded: what is returned, how it is sourced, and the injection warning. Nothing is redundant and each sentence adds distinct 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?

With no output schema, the description usefully enumerates the returned fields, standing in for a return-value spec. Read-only status is stated, and the sole parameter is fully covered by the schema; only error/edge-case behavior is unaddressed, which is a minor gap for a read tool.

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?

Schema description coverage is 100% for the single 'mint' parameter, which already documents it as a base58 SPL token mint address. The description's 'by SPL token mint' restates rather than extends that, so the baseline 3 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?

Names a specific resource (a single integrated project's live treasury), the keying dimension (SPL token mint), and enumerates the components returned: claimable pool, lock-boost pool RWA holdings and USD values, distribution split, and total fees processed. The word 'live' implicitly separates it from get_treasury_history and get_treasury_stats, 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?

There is no when-to-use or when-not-to-use statement, and no alternative is named despite many overlapping siblings (get_treasury_stats, get_treasury_history, get_my_vault, get_rwa, get_proof_of_reserves). The scope ('one integrated project', keyed by mint) is only implied by the phrasing, leaving the agent to guess which treasury tool to pick.

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