Get Mark Price Components

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 states that the call is public and requires no authentication, which is helpful. It does not describe return format or error behavior, but for a simple read/fetch operation this is adequate, though not rich in detail.

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, concise sentence that front-loads the action (Fetch) and immediately specifies the resource. It contains no padding or redundant details, making it highly effective for quick agent comprehension.

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 is simple with one parameter and no output schema, and the description states its purpose and authentication requirements. While it does not enumerate the actual components returned, this is not critical for the agent to select and invoke the tool correctly, making it sufficiently complete.

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 a description and example format. The tool description does not add any additional parameter-specific information, so the schema's high coverage (100%) carries the meaning, justifying the baseline score.

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 fetches components used to derive a mark price for a symbol, using the specific verb 'Fetch' and a precise resource. It distinguishes itself from the sibling get_mark_price by focusing on the components rather than the final 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?

The description notes that the tool is public and requires no credentials, providing a clear usage condition. However, it does not explicitly state when to use this tool over alternatives like get_mark_price or offer exclusions, so guidance is implied but not fully expanded.

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