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

With no annotations, the description carries the full burden. It usefully discloses data provenance (public TON blockchain records), the GRAM/TON currency note, and no-auth requirement. However, it omits whether lookups are cached/at what latency, and what the response shape looks like if no sales exist.

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?

One dense sentence plus a short free/no-key clause; front-loaded with the core purpose. Slightly overloaded with parenthetical currency caveat but still efficient.

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?

No output schema, so the description must convey return values, which it does by listing peak/latest sale, auction state, and bid activity. Largely complete; missing only edge-case behavior (e.g., usernames with no recorded sales) and response format details.

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% and the single 'username' parameter is documented as 'without @'. The description adds meaningful semantics about the returned data rather than repeating the schema. Baseline for a fully covered single param is 3, but the extra field-context (the *Ton fields carry GRAM amounts) adds value.

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?

Uses a specific verb ('look up') with a precise resource ('recorded market price history of a Telegram username') and enumerates exactly what data is returned (peak/latest sale, auction state, bid activity). Clearly distinguishable from siblings like namesniper_check or namesniper_alternatives.

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?

Notes it is 'free, no API key needed,' which removes a barrier, but there is no explicit when-to-use-vs-alternatives guidance. It is implied that this is for price/market data versus availability (namesniper_check) or alternatives, but that routing is left to inference.

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