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

Annotations are absent, so the description carries the full behavioral disclosure burden. It does reveal that the operation costs 0.75 USDC via x402, which is useful payment context, but it does not describe side effects, whether paymentSignature is required before execution, or what the return value looks like. Behavioral transparency is minimal beyond the price line.

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 short and the pricing detail is placed immediately after the purpose, which is economical. However, the brevity comes at the cost of necessary substance rather than from dense, information-rich prose. It is compact but under-specified.

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 paid tool with 13 parameters, no annotations, and no output schema, a two-line description is not enough to invoke it correctly. It states the price and broad purpose but omits required input semantics, optional parameter effects, and the format or meaning of the output. The payment flow and high parameter count demand substantially richer contextual guidance.

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?

Schema description coverage is 0% across 13 parameters, and the description names none of them or their roles. Terms like 'unit economics' hint that landed_cost and expected_sale_price matter, but the 11 optional fields remain unexplained in both schema and description. With no descriptions and no narrative compensation, an agent cannot determine how to set marketplace_fee_pct, returns_reserve_pct, or other optional inputs.

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 identifies a deliverable: a 'GCC opportunity score' based on 'unit economics, ROI,' so an agent can roughly infer it produces some scoring output. However, it lacks an explicit action verb and does not differentiate this tool from siblings like gcc_product_decision, gcc_portfolio_rank, or free_profit_check. This is not a tautology, but it is too vague for confident tool routing.

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?

No sentence explains when to use this tool versus alternatives, nor does it state prerequisites or exclusions. The agent is given no decision rule for choosing gf.gcc_opportunity_score over similar sibling tools. The intended use is only weakly implied by the title and phrase 'opportunity score.'

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