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

With no annotations and an output schema present, the description adds little behavioral context. It does not state that the operation is read-only, whether authentication is required, how fresh the data is, or any rate-limit behavior. It only restates output content that the output schema already covers.

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 that includes the chain, network, and data dimensions. It contains no filler or redundant phrasing, making it appropriately sized.

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 no-parameter summary with an output schema, the basic coverage is acceptable, but the description omits when to choose it over the many related summary tools (e.g., get_reputation_summary, get_trust_forensics). Given the crowded sibling space, this gap matters for correct tool selection.

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 tool takes zero parameters, so the baseline score is 4. There is no parameter syntax or filtering behavior to clarify beyond 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 names the specific resource (8004-Solana mainnet trust summary) and enumerates its contents (agents, feedbacks, trust tier distribution), making the tool's output clear. It does not, however, distinguish itself from close siblings like get_solana_agents or get_reputation_summary, so an agent still has to infer the difference.

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?

No when-to-use guidance, no alternatives, no prerequisites. The description is a noun phrase with no indication of the scenarios that select this summary over similar sibling tools. It remains merely implied that it is a broad overview.

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