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

With no annotations at all, the description carries the full burden, and it does disclose two valuable traits: the call is free and read-only (no cost, no mutation). It also hints at conditional coverage with 'catalog changes when history covers the period.' It does not say whether the address alone is sufficient authorization or what happens when no history exists.

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 sentence with no filler, and the resource list is front-loaded before the 'Free and read-only' qualifier. It is slightly dense—four resources packed into one clause with an embedded conditional—but nothing is wasted.

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 tool with no output schema and no annotations, the description adequately covers what comes back at a category level and its access cost. The main remaining gap is what happens when the wallet has no history or history does not cover the period, which the description gestures at but does not resolve.

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?

There is a single parameter with 100% schema coverage ('Your EVM wallet address'), so the schema already does the work and the baseline is 3. The description's use of 'your' reinforces self-scoping (no querying arbitrary wallets), but adds no format or validation detail 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 verb 'Read' is combined with four concrete resources (visit history, today's pulse, catalog changes, wishlist matches), which distinguishes it from the sibling tools such as answer_daily_question and claim_welcome_gift. The only weakness is that 'fresh pulse' and 'catalog changes' are domain jargon that an unfamiliar agent cannot fully decode, so the resource list is clear in shape but not entirely in substance.

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?

'Read your visit history' implies this is the go-to personal summary tool, and 'free and read-only' signals low-cost, safe invocation. However, there is no explicit when-to-use or when-not-to-use guidance, and no sibling is named as an alternative for narrower queries, so the routing signal is only implied.

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