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

With no annotations, the description carries the burden; 'intel' and 'rug check' imply a non-mutating analysis, and 'confluence' hints at how results combine. It does not explain output shape, failure modes, or costs, though the brief parameter hints at quota awareness in the schema.

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 covers purpose, scope, and the required-use gate with zero filler. The colon list is dense but readable.

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 multi-dimensional scan with no output schema, it names the intelligence categories and positions the tool as a mandatory pre-thesis step. It could add the return format or an explicit 'use for combined analysis; use siblings for single dimensions,' but the core calling context is present.

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 100%, so the baseline is 3; the description adds no parameter-level detail beyond implying 'address' refers to the token to scan. 'brief' is left to the schema, which already documents it.

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?

Describes the tool as 'Full token intel' and enumerates concrete dimensions (market, rug check, bundle/sniper analysis, social signals, confluence), which distinguishes it from narrower sibling scanners. It lacks a strong verb and specific return description, but the resource and scope are clear.

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?

States an explicit condition: 'Required before any thesis on a specific token,' telling the agent when this scan must run. It does not name alternatives or exclusions, but the mandatory precondition is a clear usage hook.

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