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

Annotations already declare readOnly/idempotent/openWorld, but the description adds real interpretive content: null means unavailable not zero, each metric carries unit, fund/global/deployment scope, source and freshness, and explicit caveats on what AUM/NAV do not imply. It omits rate limits or response shape, keeping it below 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?

Front-loaded with the core action, then caveats and freshness guidance; every sentence carries information. Slightly telegraphic run-on phrasing costs a point but nothing is wasted.

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 carry the return-value burden, and it does explain metric metadata, null semantics, and excluded data. Minor gaps remain around response structure or pagination for a tool returning multi-metric financials.

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?

With 50% schema coverage, the network enum is undescribed in the schema, but the description compensates by enumerating the exact supported networks and reinforcing the identifier's required exactness and case preservation. This adds meaning beyond the schema for both parameters.

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 and resource (get public issuer financials) scoped to exact native tokens on five named networks. It also pre-empts confusion with siblings by declaring it does not return a risk score, distinguishing it from explain_risk_score and get_native_asset_assessment.

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?

Gives clear operational guidance: preserve identifier case, requery by refreshBy for freshness, and don't interpret fund AUM/NAV as token supply or reserves. It lacks an explicit 'use X instead when...' routing statement against get_native_asset_assessment, so it stops short of the top band.

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