Get Mark Price

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

With no annotations provided, the description carries the burden of disclosing behavioral traits. It adds the authentication requirement ('Public — no credentials required') and the all-or-single market behavior. It does not mention rate limits or return format, but for a simple read-only price fetch, these gaps are minor.

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?

Two sentences, front-loaded with the core purpose, followed by parameter usage and auth context. Every word earns its place; no filler or redundancy.

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 trivial tool with one optional parameter and no output schema, the description is nearly complete. It explains what it does, how to use the parameter, and the auth profile. The only potential missing piece is an explicit statement of the return shape, but that is not critical given the simplicity.

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 already fully documents the single parameter 'symbol' with 'Omit to return all.' The description's 'Omit `symbol` for every symbol, or pass one for a single market' restates that same information without adding new meaning. Baseline 3 applies because schema coverage is 100%.

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 begins with a specific verb and resource: 'Fetch the current mark price.' It clearly distinguishes this from sibling tools like get_price (likely spot price) and get_mark_price_components (components of mark price) by using the term 'mark price'.

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?

It gives useful context: 'Public — no credentials required,' and explains how to select all vs. single market. However, it does not explicitly mention alternatives like get_price or get_ticker, nor does it explain when not to use this tool. Usage is implied rather than explicitly contrasted with siblings.

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