get_price

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

No annotations are provided, so the description carries the burden. It states the function is read-only by nature ('Precio actual'), but it does not disclose any edge cases, response format, or potential errors. For a simple getter, this is adequate but minimal.

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 sentences long, front-loaded with the purpose and including a helpful example. 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?

No output schema exists, so the description should explain the return value. It only states 'current price' but does not disclose whether the response is a plain number or a structured object. Given the tool's simplicity, this is a notable gap for an AI agent.

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?

Schema description coverage is 0%, so the description must compensate. It provides an example symbol='BTCUSDT', which clarifies the expected format (uppercase base/quote pair). This adds meaningful value beyond the bare property name, though it does not enumerate all possible symbols.

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 symbol ('Precio actual de un simbolo'). It uses a specific verb and resource, and the example symbol='BTCUSDT' clarifies the expected input. This distinguishes it from sibling tools like get_klines (historical data) and get_order_book.

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 implies usage for obtaining current price but does not explicitly contrast with alternatives like get_24h_stats or get_klines. The context is clear enough, but no when-not-to-use guidance is provided.

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