get_pricing_info

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

Annotations already declare readOnlyHint=true, so "Read-only" adds little, though "no API key needed" is useful context. The description goes beyond annotations by disclosing the concrete fee model, the fee comparison scope, and the non-escrow caveat, which materially shapes interpretation of results.

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?

Front-loads the core fee facts, then comparison scope, then the routing sentence. Dense but each clause carries information; the title duplication and "Read-only; no API key needed" are slightly redundant but not wasteful enough to penalize heavily.

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 output schema, the description carries the burden of describing returns and does so fully — fee structure, competitor comparison, and payment/approval explanation. Combined with explicit routing, an agent has everything needed to call it 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?

The tool takes zero parameters, so there is nothing for the description to disambiguate; baseline 4 applies. The description makes clear which cost concepts the call covers, which is the only relevant semantic guidance for a no-arg call.

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?

States a specific verb and resource (get fees and payment terms) with concrete detail — 1% platform fee, 3% processing charge, free joining/listing — so the agent knows exactly what this returns. It also distinguishes itself from get_platform_info by naming that sibling and its domain.

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?

Gives explicit when-to-use ("cost questions or before quoting a total to the account owner") and names the alternative (get_platform_info) with its selecting condition ("what the platform is and how it works"). Routing is unambiguous.

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