get_price

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

No annotations are provided, and the description does not disclose behavioral traits such as network calls, rate limits, authentication needs, or what the 'period' parameter means. The description implies a single price, but the 'period' parameter suggests historical data, creating ambiguity and contradiction.

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, concise but too brief for a tool with untrivial input parameters. It lacks structure and does not front-load critical information beyond the basic purpose.

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 no output schema and unannotated parameters, the description does not explain what the tool returns (e.g., a number or object) or how the period affects the output. The context is incomplete for effective use, especially with the ambiguous period parameter.

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 has 2 parameters (ticker, period) with 0% description coverage. The description does not explain the parameters or their expected values (e.g., what '1d' means or other valid periods), adding no value beyond the schema. The agent must infer usage from parameter names alone.

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 gets the price of a stock/crypto ticker, with a specific verb and resource. It distinguishes itself from the sibling 'get_news' by the type of data returned. However, it does not clarify whether it returns current or historical prices, leaving some ambiguity.

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?

There is no guidance on when to use this tool versus alternatives, nor any mention of limitations, prerequisites, or when not to use it. The only sibling is 'get_news', but no explicit comparison is made.

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