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

Annotations already declare readOnlyHint=true, destructiveHint=false and openWorldHint=false, so the safety profile is covered. The description does add genuine context beyond that with 'point, or pointed, at', revealing that historical/stale destinations are indexed and retrievable, but it says nothing about ordering, result-size behavior, or how 'current destinations' is determined.

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 sentences, no boilerplate, with the dataset definition first and the filtering capability second. The opening clause is syntactically dense ('Smart contracts that compromised websites read their next stage from'), costing a small amount of readability but no wasted content.

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 four-optional-filter search tool with no output schema, the description usefully enumerates the returned fields, which compensates for the missing output schema. The remaining gap is how multiple filters interact and what result volume to expect, both of which an agent would need before a broad unfiltered call.

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 coverage is 75%, with descriptions for kit, chain and destination already in the schema, so the structured data does most of the work. The description adds meaning only for destination, clarifying it matches the pointer relationship to a host rather than a text substring; limit is undocumented in both places.

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 identifies the resource precisely: smart contracts used in EtherHiding that compromised sites resolve their next stage from, and it names the tracked fields (chain, kit, destinations, last-read time). It stops short of an explicit search verb and never names the sibling get_etherhiding_contract, so an agent must infer the list-vs-single distinction from the tool names alone.

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?

One concrete usage path is spelled out: set destination to find contracts that point or pointed at a host, which implies kit/chain narrowing by analogy. There is no explicit statement of when to prefer this over get_etherhiding_contract, no note that all filters are optional and combine, and no guidance on unpivoted listing behavior.

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