indicators

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

Without annotations, the description carries the burden. It does disclose that the tool returns quotes and sparkline data, implying read-only behavior, but it doesn't elaborate on error handling, rate limits, or what invalid list IDs do. This is sufficient for a simple quote tool but not exhaustive.

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 filler words. It efficiently conveys the domain, purpose, and extra data (sparkline).

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 simple optional parameter and no output schema, the description provides enough context to understand the tool's role. It doesn't detail the return structure, but the mention of quotes and sparklines gives a reasonable picture. However, it could clarify the relationship to the sibling 'indicator' 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?

The description adds meaning to the 'list_id' parameter by giving concrete examples (FI_INDEX_GLOBAL, CURRENCY_GLOBAL) and framing it as a market list selector. Since the schema has no parameter descriptions, these examples are valuable, though the description does not enumerate all possible list IDs or explain the default behavior.

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 identifies the tool as providing Index/FX quotes for a market list, with examples of valid list IDs. It distinguishes itself from the singular 'indicator' sibling by focusing on lists and including sparkline data, though it lacks an explicit verb like 'retrieves'.

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 for when to use this tool over alternatives like 'indicator' or 'quote'. There is no mention of exclusions, prerequisites, or contrasting use cases.

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