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

With no annotations, the description carries the full burden of explaining behavior, but it only repeats the tool name. It discloses nothing about read/write side effects, required authentication, network/chain semantics, pagination, or what data is returned.

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 text is short but not concisely informative; it is under-specification that merely echoes the name. There is no front-loaded action, no structure, and no content that earns its place.

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 4-parameter tool with no annotations, no output schema, and an enormous sibling list including many wallet tools, the definition is completely inadequate. An agent has no basis for selecting, parameterizing, or interpreting the result of this tool.

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 description itself adds no parameter meaning, but schema description coverage is 100% and each parameter has a '... to process' description, which technically satisfies the high-coverage baseline. The baseline is not raised because the schema descriptions are generic and do not explain formats, defaults, or how wallet and address differ.

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 is a verbatim restatement of the tool name ('Wallet Activity: Wallet Activity') and provides no verb, resource, or outcome. An agent cannot tell whether this returns transaction history, token transfers, or something else, and it does nothing to distinguish the tool from dozens of wallet-related siblings.

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 guidance on when to use this tool rather than wallet-balance, wallet-tokens, wallet-report, wallet-scan, or other wallet tools. No conditions, exclusions, or alternatives are mentioned.

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