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

No annotations are provided, so the description must carry the full burden. It mentions a cost of $0.003, which is a useful transparency cue, but it does not disclose that the operation is read-only, any rate limits, or whether it requires authentication. The cost hint is helpful but insufficient.

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?

The description is concise, a single sentence that front-loads the purpose and scope. It is efficient with no waste, though it omits important behavioral and parameter details.

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 annotations, 0% schema coverage, and an output schema present (but not described), the description is incomplete for a tool that accepts 1-10 addresses and has an optional agent_id. It does not explain the output structure, any error conditions, or the relationship to sibling tools like ddg_crypto_price.

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%, so the description must explain parameters. The description says '1-10 addresses' and mentions ethereum/base, but does not explain that the 'addresses' parameter is an array or string, nor the format for the optional agent_id. It adds little 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?

The description states a specific resource (crypto portfolio), the action (consolidated USD value), and scope (1-10 addresses, native + USDC on ethereum/base). It is clear but does not explicitly differentiate from siblings like ddg_crypto_price or ddg_wallet_snapshot, though the scope hint helps.

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 explicit guidance on when to use this tool versus alternatives like ddg_crypto_price or ddg_wallet_snapshot. The description implies it is for portfolio valuation, but no when/when-not conditions or alternative names are given.

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