pyth_getPriceHistory

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

With no annotations, the description bears full burden of disclosure. It only states the general function without revealing behavior such as output format (array vs. single object), supported price IDs, rate limits, or potential pagination. This lack of detail hinders the agent's ability to handle the tool appropriately.

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, which is concise but overly sparse. It meets the minimum requirement of stating the purpose but omits critical details that would improve usability without becoming verbose.

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 complexity (2 parameters, no output schema), the description is insufficiently complete. It does not explain the output structure, the effect of different periods, or any prerequisites. The agent is left with significant ambiguity about how to interpret the results or handle errors.

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%, and the description provides no explanation of the 'priceId' or 'period' parameters. The agent must rely solely on the schema, which only lists names and types. The description adds no value beyond the schema, failing to specify allowed values for 'period' or the meaning of 'priceId'.

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 it retrieves historical price data from Pyth oracle, distinguishing it from siblings like pyth_getPrice (current price) and pyth_listPriceFeeds (feed list). However, it lacks specifics on the nature of the historical data (e.g., time range, granularity).

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 over alternatives. The description does not mention that this should be used for historical queries while pyth_getPrice is for current data, missing an opportunity to aid tool selection.

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