pyth_getPrice

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

With no annotations, the description must disclose behavioral traits. It states the action ('get current price') but lacks details on what the return value looks like, potential errors, or dependencies. For a simple read operation, it is adequate but leaves the agent without full insight into the response structure (no output schema).

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, front-loaded sentence with no wasted words. Every part is essential and directly communicates the tool's 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?

For a simple price fetch tool, the description is sufficient. However, the absence of an output schema and lack of error handling details slightly reduce completeness. The simplicity of the tool justifies a high score.

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 no new meaning beyond the schema's parameter description, which is already clear. Since schema coverage is 100% and the schema description is explicit, the baseline score of 3 is appropriate.

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 current price from a Pyth on-chain oracle feed, using a specific verb and resource. It distinguishes itself from siblings like pyth_getPriceHistory and pyth_listPriceFeeds which handle historical data and feed listing respectively.

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 when the current price is needed but provides no explicit guidance on when not to use it or mention of alternatives. The context of sibling tools is available but not leveraged in the description.

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