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

Annotations already declare readOnlyHint=true, idempotentHint=true, openWorldHint=true, and destructiveHint=false, so the safety profile is fully covered. The description adds useful behavioral context by naming the data source (on-chain ERC721 events) and the derived metrics, but says nothing about rate limits, freshness, or failure modes; with annotations doing the heavy lifting a 3 is appropriate.

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 front-loaded sentence with the verb and resource first, followed by the analyzed signals. No filler, though the colon-list format is dense and could be split for readability.

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?

The tool is low-complexity (2 params, 100% schema coverage, output schema present, rich annotations), so the description does not need to explain return values. What it states is accurate and sufficient; only the missing sibling/usage orientation keeps it from a 5.

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%: the address param is described and the chain param carries a full enum plus supported-chain list and a default of "base". The description adds no parameter-level meaning beyond the schema, 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 ("Analyze") and resource ("NFT collection activity"), then enumerates the concrete outputs: recent transfers, mints, burns, unique buyers, activity level, sourced from on-chain ERC721 events. It is clear what the tool returns, but it does not distinguish itself from nearby siblings nft.collection, nft.holders, or nft.metadata, and the name nft.floor vs. the title/description (activity, not floor price) creates mild ambiguity.

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 gives no when-to-use guidance, no prerequisites, and never names an alternative among the NFT siblings (nft.collection, nft.holders, nft.metadata). An agent must infer usage purely from the purpose statement.

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