Estimate Flip Profit

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

Beyond the readOnlyHint annotation, the description additively discloses that it is 'ESTIMATE ONLY', that guide prices lag the live market, and that buy limits/fill times are not modelled. This clearly sets expectations that actual profit will differ, providing substantial behavioral context.

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 sentences: the first states the core purpose and inputs, the second adds essential caveats and parameter guidance. No redundant or filler content, front-loaded with the primary function.

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 a read-only annotation, no output schema, and 5 optional parameters, the description fully covers what the tool does, its limitations, and how to customize inputs. It is self-contained and leaves no critical gaps for an agent to invoke correctly.

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?

Although the schema already provides 100% parameter descriptions, the description adds meaningful guidance by stating 'by itemId or name' and instructing users to 'Pass buyPrice/sellPrice to model your own offers', which clarifies parameter usage and optionality beyond the schema.

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 a specific verb ('Estimate') and resource ('Grand Exchange flip profit'), including the 2% RS3 sales tax. It also specifies the input method (by itemId or name), which distinguishes it from sibling tools like get_item_price or lookup_item.

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?

It provides context on when to use this tool (for flipping profit estimates) and warns about limitations (guide prices lag, buy limits/fill times not modelled). However, it does not explicitly name alternative tools or state when NOT to use it, though the caveats imply it shouldn't be used for live-market decisions.

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