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

Annotations already declare readOnlyHint=true and destructiveHint=false, so safety is covered. The description adds real context beyond that: the values are read live from the chain, they are the fee-on-transfer parameters a naive swap would fail without, and it gives concrete measured numbers (3% tax, ~6% slippage for a ~$100 trade). It does not discuss caching/freshness or chain selection, keeping it below a 5.

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?

Front-loaded with the core purpose and the returned values, and the closing sentences carry the routing guidance. However, the second sentence is a long, densely nested construction with stacked parentheticals (the 3%/6%/$100 figures inside a clause about the settings) that is harder to parse than it needs to be.

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 burden of explaining return values and does so by enumerating every field the agent will receive, plus what to do with them. What is missing is freshness/staleness behavior and the target chain, but for a zero-parameter read tool this is nearly complete.

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 there is nothing for the description to disambiguate; baseline is 4. The description correctly implies a no-argument, read-everything-necessary call.

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?

Names a specific resource (the DEX parameters for a $BOBAI trade) and enumerates exactly what is returned: PancakeSwap V2 router, pair, both swap paths, fee-on-transfer tax and slippage, and the SupportingFeeOnTransferTokens method names. It is clearly distinguishable from siblings like bobai_token_info, bobai_price, and bobai_purchase_guide.

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?

Explicitly states the use condition ('Use it before writing your own swap code') and names the alternative with the condition that selects it ('for ready-made code use bobai_purchase_guide'). It also warns that a naive swap reverts without these numbers, which is a concrete reason to call it.

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