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 explicitly discloses the key safety-relevant behavior: no funds are moved. This is the most important behavioral trait for a quote/calculation tool. It does not go further into side effects or state changes, but for a non-mutating calculator this is reasonably transparent.

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 front-loaded sentence with no filler. It states the action, the outputs, and the key safety constraint compactly. 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?

The tool has no output schema and no annotations, so the description should explain return behavior and default behavior for the optional take_rate_bps. It does neither. It is unclear what happens when take_rate_bps is omitted, whether the take rate is an input or an output, and what shape the quote result takes. For a fee-quote tool this is a meaningful gap.

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%, so the description must compensate for missing parameter meaning, but it does not clearly map the inputs. 'gross_amount_usdc' and 'take_rate_bps' are never explained, and the relationship between the optional take_rate_bps input and the described 'calculate marketplace take rate' output is ambiguous. The description adds little beyond the parameter names already present in 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 states a specific verb ('Calculate'), a precise resource ('marketplace take rate and provider net'), and an explicit boundary ('without moving funds'). This clearly distinguishes it from execution-oriented siblings like gf.execute and from generic quoting tools, since it names exactly what it computes.

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 phrase 'without moving funds' implies the tool is for estimation rather than execution, which is a useful context cue. However, the description does not explicitly say when to prefer this over siblings such as gf.quote or gf.execute, nor does it name alternatives or provide exclusions. The usage guidance is implied rather than stated.

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