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

No annotations are provided, so the description carries the full burden. It discloses an important cost of $0.15 Base USDC, adding useful behavioral context. It does not mention side effects, authentication, output behavior, or whether the supplied records are sent somewhere, but for a primarily analytic tool the cost disclosure partially compensates.

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 compact and front-loaded, placing the main purpose before the cost note. Every sentence adds information, and there is no filler or redundant repetition of the tool name.

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?

Given the absence of annotations and an output schema, plus an almost fully open-ended input schema, the description is too thin for an agent to confidently invoke the tool. It lacks input format details, expected output description, and any guidance on how the supplied transaction records should be passed. The cost note is helpful but does not resolve these gaps.

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?

The input schema defines a single 'input' object with no properties and additionalProperties allowed, and schema description coverage is 0%. The description says the tool works 'from supplied public transaction records,' which indicates what belongs in the input object, but it does not specify how the records should be structured, what fields are expected, or what format is required. This leaves significant ambiguity.

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 that the tool produces a wallet activity summary from supplied public transaction records, naming both the resource (wallet activity) and the data source. It goes beyond a tautology, though it does not explicitly use a verb like 'generates' and does little to differentiate from sibling summary/report tools beyond the wallet-specific topic.

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 phrase 'from supplied public transaction records' implies the tool should be used when such records are available and a wallet activity summary is desired. However, it gives no explicit guidance on when to use this tool versus alternatives, no exclusions, and no mention of prerequisites or input format expectations.

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