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

The description explicitly states it does not change fixed settlement prices, which is a genuine behavioral guarantee beyond the schema and beyond the absent annotations. However, it is silent on whether the tool mutates anything else, executes a transaction, or is read-only, so behavioral disclosure is only partial.

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 a single concise sentence with no filler, and the key constraints are front-loaded. It is appropriately sized for a tool description and contains no redundant restatement of the schema.

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 annotations, no output schema, and seven undocumented parameters, a single vague sentence leaves out nearly everything needed for correct invocation: parameter semantics, required fields, output shape, side effects, and distinction from sixteen sibling tools. The description is far from complete for a tool of this complexity.

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 schema contains seven parameters with 0% description coverage, and the description references only an abstract 'agent budget' without mapping to any specific field. It does not clarify the roles of goal, task, intent, product_count, budget_usdc, max_spend_usdc, or description, leaving the agent unable to determine what to pass.

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 states an action ('choose'), a resource ('GF commerce outcome'), and constraints ('within the agent budget', 'without changing fixed settlement prices'), so it is not a tautology. However, 'highest-value GF commerce outcome' is vague and does not define what an outcome is or what quoting entails, and it does little to distinguish this from siblings like gf.gcc_opportunity_score or gf.free_profit_check.

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 only usage signal is the budget and fixed-price constraint, from which an agent might infer a selection task under budget limits. It names no alternatives, no conditions for when to prefer this over gf.execute or gf.marketplace_fee_quote, and no when-not-to-use guidance.

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