simulate_trade

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

With no annotations provided, the description carries the full burden of behavioral disclosure. It effectively states that this is a simulation tool ('Does NOT execute a trade'), which clarifies it's non-destructive and likely read-only. It also adds useful context by specifying the bonding curve formula used for calculations. However, it lacks details on potential limitations like rate limits, error conditions, or authentication needs.

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 front-loaded with the core purpose in the first sentence, followed by critical behavioral context ('Does NOT execute a trade') and technical details (the bonding curve formula). Every sentence earns its place by adding essential information without redundancy, making it highly efficient and well-structured.

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?

Given the tool's complexity (simulation with a bonding curve formula), no annotations, and no output schema, the description does a good job of covering key aspects: purpose, non-execution behavior, and the calculation method. However, it lacks information on output format (e.g., what the simulation returns) and any error handling, which would be beneficial for full completeness.

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 input schema has 100% description coverage, providing clear details for all three parameters (symbol, side, amount). The description adds minimal value beyond the schema, as it only implicitly references the parameters through the explanation of buy/sell scenarios. Since schema coverage is high, the baseline score of 3 is appropriate, as the description doesn't significantly enhance parameter understanding.

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 clearly states the specific action ('simulate a buy or sell trade'), the resource ('tokens'), and the purpose ('estimate how many tokens you'd receive for a given USDC amount or vice versa'). It explicitly distinguishes itself from execution tools by stating 'Does NOT execute a trade,' which is crucial for differentiation from potential siblings that might perform actual trades.

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 provides clear context for when to use this tool: to estimate token amounts before executing a trade, specifically for buy/sell simulations. However, it does not explicitly mention when not to use it (e.g., for actual trading) or name alternatives among the sibling tools, such as which tools might handle real trades or other related functions.

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