Get Stock Token quote

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

Given readOnlyHint and openWorldHint annotations, the description adds useful behavioral context by detailing the types of prices returned (oracle vs DEX, premium/discount, multiplier) and the underlying share price. It does not mention error states or data provenance beyond the oracle, but annotations already cover the read-only safety profile.

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 sentence that front-loads the verb and resource, then uses a colon to list output components. Every phrase adds value, with no redundant or promotional language.

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?

Since there is no output schema, the description compensates by listing the key return fields (oracle price, DEX mid, premium/discount, multiplier, share price). It does not mention possible errors or currency, but for a read-only quote tool it is 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 input schema already provides 100% parameter descriptions (e.g., symbol is a ticker, maxAgeSeconds rejects stale Chainlink answers). The description only reinforces 'by ticker' and adds output semantics, not new parameter meaning, so it does not exceed the schema baseline.

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 starts with a specific verb 'Price' and resource 'Stock Token by ticker', and enumerates the exact price components (Chainlink oracle, Uniswap mid, premium/discount, ERC-8056 multiplier, underlying share price), clearly distinguishing it from siblings like get_coin or list_stock_tokens.

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 clearly implies usage for pricing a single stock token by ticker, and the mention of tickers and price details sets the expected context. However, it does not explicitly contrast with alternatives or state when not to use this tool.

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