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 discloses the $0.01 USDC cost, which is useful, but it does not mention whether the operation is read-only, what happens when prefer_async is used, what a result looks like, or any failure behavior. The phrase 'measured precision' is vague and unexplained.

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 two short sentences with no filler. The primary purpose is front-loaded, and the cost information is a discrete, useful second sentence that earns its place.

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 tool with no output schema and an async-related parameter, the description is incomplete. It does not explain prefer_async, the relationship to get_job_result, or what information is returned. The cost and purpose are present, but an agent would not know how to handle the async path or interpret results.

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 the description does not explain the 'mint' parameter or the 'prefer_async' boolean. It also fails to mention that prefer_async likely relates to the job/result flow visible in sibling tools. The description adds no meaning beyond the bare schema field names.

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 states a specific verb ('Check') and resource ('pump.fun token rug flags and measured precision'), which clearly indicates the tool's purpose. It is distinct enough from sibling check_solana_transaction by focusing on token risk, though it does not explicitly name or contrast with any sibling.

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 description gives no guidance on when to use this tool versus check_solana_transaction, get_job_result, or retry_failed_job. It also does not mention any prerequisites, context, or exclusions. The only usage hint is the cost, not a selection condition.

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