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

Annotations already declare readOnlyHint=true and destructiveHint=false, so the safety profile is covered. The description adds useful return-format context by stating it returns a raw wei amount and a human-readable formatted value, which goes beyond the annotations. It does not cover auth, rate limits, or edge cases, but for a simple read tool this is solid.

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?

Two tightly written sentences with no filler. The purpose and scope are front-loaded, and the return format follows immediately without wasted words.

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 one-parameter, read-only query with annotations and no output schema, the description is nearly complete: it states what the tool returns and the scope of the aggregation. It could be stronger by clarifying how it differs from sibling fee-related tools, but no critical invocation detail is missing.

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%, and the single parameter is fully documented in the schema as an ERC-20 token contract address. The description reinforces the token scope but adds no new syntax or format details beyond what the schema already provides, 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?

States a specific verb and resource: getting total protocol fees for a specific ERC-20 token address across all escrows. It also names the return content (raw wei and formatted value). However, it does not explicitly differentiate itself from related siblings such as protocol_fee, protocol_escrow_fees, or pcc_protocol_fee.

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?

The description implies the tool is used to look up aggregate fees for one token, but it provides no explicit when-to-use guidance, prerequisites, or alternatives. It never says when to prefer this over protocol_fee or protocol_escrow_fees.

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