get_ticker

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

No annotations are provided, so the description carries the full burden. It discloses that the tool is public and returns specific data fields, but lacks details on rate limits, data freshness, or any side effects. Basic transparency is present but not comprehensive.

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 two concise sentences: the first states the tool's purpose, the second adds public nature and an example. Every sentence provides essential information with no redundancy or wasted words.

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?

Given the tool's simplicity (one parameter, no output schema), the description covers the main aspects: purpose, public access, and example. It lacks explicit details about return format or data freshness, but the mention of 'last price, bid/ask, 24h stats' gives sufficient context for most use cases.

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 single parameter 'market_id' is fully described in the schema with an example. Schema description coverage is 100%, and the tool description reinforces the example. The description adds value by providing a concrete example format beyond the schema's generic description.

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 retrieves the ticker (last price, bid/ask, 24h stats) for a specific market. It includes an example market ID, distinguishes the tool from siblings (e.g., get_orderbook, list_markets), and notes the public nature.

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 explicitly says 'Public — no credentials needed,' providing clear guidance on when to use it. It doesn't explicitly state when not to use it or list alternatives, but the context of sibling tools and the tool's specific purpose imply appropriate usage scenarios.

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