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

With no annotations, the description carries the full behavioral burden, and it discloses only that the call is free. It does not state that the operation is read-only, what the response looks like, whether authentication is required, or any limits, leaving the mutation/safety profile entirely unstated.

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 compact sentence with the key 'FREE' qualifier front-loaded, so it is not verbose, but the heavy use of undefined internal terms makes it less clear than its length suggests.

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 zero-parameter, no-output-schema informational tool the description is minimally sufficient, but with no annotations it should at least state that the operation is a safe read and clarify what the buyer-facing summary returns.

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 and the schema is trivially complete, so there is nothing for the description to compensate for; baseline 4 applies.

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 name and description both indicate a descriptive/informational tool that summarizes paid tools, but the sentence is dense with unexplained jargon ('sol-defi-desk', '/sponsor /ledger', 'openly AI operator Survivor') and gives no sense of what the summary actually contains or how it differs from the sibling mint_preflight/token_check tools.

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 'FREE:' prefix hints this is a no-cost operation as opposed to the paid tools it describes, which is a mild usage cue, but there is no explicit when-to-use guidance, no prerequisites, and no routing to or away from any alternative tool.

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