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

With no annotations provided, the description carries the full burden of behavioral disclosure, but it only says 'Map ... to a token.' It does not clarify whether this is a read-only lookup, what the output looks like, whether it fetches live data, or whether any side effects occur. The description is not misleading, but it is too sparse to provide adequate transparency.

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?

The description is a single, focused sentence that front-loads the core operation and immediately enumerates the key signal categories. There is no filler, repetition, or unnecessary detail, so the structure earns a high score.

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 single-parameter data-lookup tool with no output schema and no annotations, the description is minimally viable: it tells the agent what data sources are involved and that the result is mapped to a token. However, it omits return format, address format, and the distinction between this and similar sibling tools, leaving meaningful gaps for an agent trying to use the result correctly.

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?

The input schema has one required string parameter named 'address' with 0% schema description coverage. The tool description does not explain what format the address should take, which blockchain it refers to, or how it relates to the token mapping. 'Address' is somewhat self-explanatory, but the description adds no semantic detail to compensate for the empty 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 description states a clear operation ('Map') and a specific resource (a token), and enumerates the signal types (X/Telegram/web, DexScreener boosts, paid profiles, community takeovers). This gives the agent a solid sense of what the tool does. It does not explicitly distinguish it from siblings like talon_social, but the enumerated sources and 'signals' framing are sufficiently distinctive.

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 offers no guidance on when to use this tool versus alternatives such as talon_social or talon_scan. There is no stated prerequisite, no comparison to siblings, and no mention of what kind of token address is expected. The usage context is only implied by the description's content, not explicitly communicated.

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