Get sponsorship price quote

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

The description reinforces the read-only annotation and adds critical usage behavior: always call before sponsor_listing and show the quote. This goes beyond the annotation by providing a protocol for the agent. It omits mention of error cases but is sufficient for a simple read operation.

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?

Single sentence with endpoint appended, no fluff. Every word adds value, and the instruction is front-loaded. Ideal length.

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, but the description implies the quote is returned ('show the quote'). It doesn't specify the return format, but the simplicity of a price quote and the openWorldHint make this acceptable. Could mention that the quote is a numeric value.

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 coverage is 100%, so the description does not need to elaborate on parameters. The description adds no extra semantics beyond what the schema provides, meeting the baseline of 3.

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 the tool's purpose ('Get a price quote for sponsoring a listing') and includes the endpoint, making it distinct from siblings like sponsor_listing. It specifies the action (get), resource (sponsoring a listing), and context.

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?

Explicit guidance: 'Read-only — ALWAYS call this and show the quote to the user before sponsor_listing.' This tells the agent exactly when to use it and what to do with the output, clearly differentiating it from sponsor_listing.

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