获取国际贵金属价格

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

There are no annotations, so the description carries the burden. It discloses that prices are 'real-time' and lists covered instruments, which adds some behavioral context. However, it does not mention output format, potential delays, or error behavior. For a simple read-only getter, this is adequate but not rich.

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, focused sentence that front-loads the primary function and then adds specific examples. 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?

For a tool with one optional parameter and no output schema, the description plus parameter schema provide sufficient context. It explains the real-time nature and the covered instruments. It does not describe return structure, but that is not essential for such a simple price lookup tool.

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 coverage is 100%: the only parameter 'symbol' has a description enumerating supported values. The description text repeats the same list without adding new meaning. Baseline 3 is appropriate because the schema fully documents the parameter.

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 fetches real-time international precious metals prices, listing specific instruments (London Gold, London Silver, COMEX Gold, COMEX Silver). This specifies the verb and resource. It does not explicitly contrast with sibling tools like pm_spot_prices, but the scope is clear enough to differentiate from most siblings.

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 provides clear context: this tool is for international precious metals prices. There are no explicit exclusions or alternative recommendations, but the context implies when to use it. It does not explicitly say when not to use it, but that is not necessary given the narrow scope.

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