get_artemis_supported_metrics_for_symbol

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

The word 'Get' implies a read-only operation, but the description does not explicitly state side effects, authentication requirements, rate limits, or error behavior. Since no annotations are provided, the description carries the full burden, and it only partially addresses behavioral context.

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 concise and directly to the point. It avoids unnecessary fluff and clearly communicates the core function and the key constraint on the symbol parameter in two short sentences.

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?

The description mentions that the tool returns metrics with descriptions and sources, giving an agent a reasonable idea of the output. However, with no output schema, details about response structure, pagination, or possible empty results are not covered, though the tool's simplicity keeps this from being a major gap.

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 schema only defines 'symbol' as a required string with no description. The tool description adds that it accepts only one symbol at a time, which is useful, but it does not clarify the expected format (e.g., ticker symbol, name) or provide examples, leaving some ambiguity.

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's purpose: to get the list of metrics supported by Artemis for a given symbol, including their descriptions and sources. It uses a specific verb ('get') and identifies the resource ('metrics'), making the intent unambiguous.

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 some usage guidance by explicitly noting that the symbol parameter accepts only one symbol at a time. However, it does not mention when to prefer this tool over sibling tools like get_artemis_data or how it relates to them, so guidance is partial.

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