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

No annotations exist, so the description carries the full behavioral burden. It discloses the 0.012 USDC fee, which is useful, but 'sign' implies an on-chain/write action and key requirements that are never explained, and nothing is said about reversibility or failure modes.

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 core action front-loaded and the cost appended. It is efficient and waste-free, though arguably too terse for a four-parameter tool.

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 tool with nested object parameters, 0% schema coverage, no output schema, and no annotations, the description leaves too much unexplained: parameter shapes, signing requirements, and return behavior are all absent.

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 0% across 4 parameters (3 required), including nested objects like asset/previous_state/current_state. The description only hints at attributes ('NAV, income, maturity, redemption or freeze state') that likely live inside those state objects, leaving source_urls and the nested shapes undocumented.

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 specific verbs (detect, sign) and a concrete resource domain (material RWA changes in NAV, income, maturity, redemption, freeze state), which is far more informative than the bare name. It does not, however, distinguish itself from siblings like rwa_nav_reserve or rwa_compliance, so the agent must infer boundaries.

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?

No when-to-use guidance, no prerequisites, and no alternatives are named despite dense sibling overlap (rwa_nav_reserve, rwa_compliance, rwa_asset_due_diligence). The only routing-adjacent info is the price tag, which is not usage guidance.

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