get_price

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

The description only states it returns 'Current price information' without elaborating on data freshness, rate limits, or other behavioral traits. With no annotations, the description bears full responsibility but offers minimal transparency.

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 extremely concise, with a single sentence for the main purpose and clear Args/Returns sections. Every part is necessary and no extraneous information is present.

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 and the presence of an output schema (signaled), the description covers the basic purpose and parameter. However, it omits any mention of data source, latency, or edge cases, which would be helpful for a complete understanding.

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 description adds value by providing examples for the symbol parameter (e.g., BTCUSDT, ETHUSDT), which the schema lacks due to 0% description coverage. However, it does not explain the expected format or constraints beyond the examples.

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 returns the current price of a cryptocurrency. The verb 'Get' and resource 'price' are specific, and it distinguishes from sibling technical indicator tools.

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?

No guidance is provided on when to use this tool versus the many sibling tools. It does not specify prerequisites or conditions, leaving the agent to infer usage context.

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