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

With no annotations, the description carries the full burden of behavioral disclosure. It reveals a key behavior: the price moves along the curve with each trade, and instructs the agent to read the price first. However, it doesn't disclose whether the tool itself is read-only or mutating, or any other operational details.

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?

Two sentences with zero waste. The purpose is front-loaded, and the crucial behavioral warning about price movement is placed second. Every word 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 how-to guide, the description is minimal. It provides the key action (read price first) but doesn't outline the full trading process or mention any prerequisites or outcomes. Given there are no parameters or output schema, it's acceptable but not thorough.

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 has zero parameters, so per the baseline rule this dimension is scored 4. There is no schema detail to compensate for, and the description's mention of price behavior is not parameter-related.

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 it's a how-to guide for buying or selling NFTs on the bonding-curve marketplace, specifying the resource and action. It doesn't explicitly contrast with sibling how-to tools like commodity_how_to_trade, but the resource is specific enough to distinguish it.

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 implies when to use it (when trading NFTs on the bonding-curve marketplace) but does not provide explicit alternatives or exclusions. Siblings include many other how-to guides, but no guidance is given on when to choose this one over them.

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