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

Annotations only declare readOnlyHint and openWorldHint; the description goes well beyond them by disclosing the paid-call model, the exact price ($0.03 USDC via x402 on Base mainnet), and the failure/retry protocol (PaymentRequired challenge, then replay the identical call with the signed payload in _meta['x402/payment']). That is precisely the kind of non-obvious operational behavior an agent must know before calling.

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?

Purpose and return contents are front-loaded in the first sentence, with payment mechanics last where they belong. The output enumeration is dense but each item is distinct and decision-relevant; only minor tightening is possible.

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?

With no output schema, the description carries the return-value burden and does so by naming the result categories (actor links, phishing kits, hosting indicators, abuse categories, WAF hint). Payment prerequisite and retry semantics are fully covered, leaving nothing an agent needs missing.

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% with only two params, both already documented with examples (AS215540, hivelocity). The description adds no parameter-level meaning, 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 and resource ('Profiles an ASN') scoped to ICS threat actor infrastructure use, then enumerates concrete outputs (actor associations, phishing kits, bulletproof hosting, abuse categories, blocking recommendation). No sibling tool in the list does ASN-level infrastructure profiling, so the agent can route to it without opening the schema.

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?

Usage is implied by the required 'asn' input and the ICS/OT framing, but there is no explicit when-to-use statement and no named alternative (e.g., getIocEnrichment or getThreatActor) for overlapping infrastructure questions. Guidance is inferable rather than stated.

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