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

No annotations are provided, so the description carries the full burden. It implies a read operation but says nothing about permissions, rate limits, whether this is a pure read or triggers analysis, or what the flags mean. The only behavioral hint is the list of metric names.

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?

It is a single terse fragment that is well front-loaded, but the brevity here reflects under-specification rather than tight conciseness. It reads more like a label than a usable definition.

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?

An output schema exists, so return-value shape need not be described. However, with no annotations, 0% parameter coverage, and no usage or behavioral context, the definition leaves too much unresolved for an agent to invoke it confidently.

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 0% and neither parameter is mentioned in the description. 'limit' is self-evident, but 'risk' is an untyped free-form string with no enum, no default meaning, and no documentation anywhere, leaving an agent unable to populate it correctly.

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 names a specific domain (Solana sybil forensics) and enumerates the exact signals it surfaces: reviewer concentration, ghost ratio, burst, and flags. This differentiates it from siblings like get_solana_trust_summary and get_solana_agents. The typo 'forensika' and the absence of a clean verb ('retrieve/analyze') keep it just short of a 5.

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 statement of when to reach for this tool versus the many sibling trust/forensics tools, nor any prerequisite or exclusion. An agent must infer usage purely from the metric names. No alternative routing guidance is given.

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