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

Annotations already declare read-only, idempotent, non-destructive, closed-world behavior, so the bar is lower. The description still adds real value: it is free to call, it indexes only the ~300K coins that completed their bonding curve, and it returns a specific field set including deployer stats, graduation flag, and market cap snapshots.

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?

Dense with useful information but delivered as one run-on sentence with a dangling opening fragment ("Free.") and an awkward embedded field list. Every fact roughly earns its place, but the structure does not front-load the action and is harder to parse than necessary.

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?

With no output schema, the description carries the return-value burden and does so by naming the returned fields and ordering. The coverage limitation and free-call status round out what an agent needs; only the empty-result behavior is unaddressed, which is minor for a simple lookup.

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%, so both q and limit are already fully documented, including the $KIMCHI/KIMCHI forms and the default of 20. The only semantic addition is that passing a mint returns that coin's name, which is marginal beyond the schema; baseline 3 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?

It states a specific verb and resource — look up pump.fun coins by ticker, name, or mint, newest first — and names the sibling to follow with (launch_record on the mint). The opening clause is grammatically broken ("The pump.fun coins a ticker or name means"), which costs clarity but not comprehensibility.

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?

Concrete use cases are enumerated ("what is $KIMCHI's CA", "which Kimchi is the real one", "find this coin by name") plus a routing hint to launch_record once the mint is known. The key exclusion is also stated — coins still on their bonding curve are not covered — though no alternative is offered for those.

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