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

With no annotations, the description carries the behavioral disclosure burden. It adds useful context about data provenance: live Robinhood Chain token profiles, X handles, and matching to on-chain activity. However, it does not state whether the operation is read-only, what output shape to expect, or any freshness/rate-limit caveats.

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 compact sentence with the core concept front-loaded and no filler. It conveys source, match logic, and scope efficiently, though it is slightly jargon-heavy.

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?

There is no output schema, and the description does not explain what the returned data looks like, how limit affects results, or what 'on-chain activity' means in practice. For a tool with one parameter and many siblings, this leaves important context 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?

The only parameter, limit, has schema constraints (default 30, min 1, max 50) but the description never mentions it. With 0% schema description coverage, the description should compensate, but it adds no semantic meaning for the parameter.

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 clearly identifies the tool's output domain: a cross-token social graph linking X handles from live Robinhood Chain token profiles to on-chain activity. It is specific enough to distinguish from many sibling tools, though it lacks an explicit imperative verb such as 'Get' or 'List'.

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?

There is no guidance on when to use this tool versus the many talon_* siblings, nor any exclusions or alternative tool references. The description only implies it is for social-graph data, leaving the agent to infer selection criteria.

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