Index card and index history

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

Annotations already declare read-only, idempotent, open-world, non-destructive behavior. The description adds useful source-specific behavior: Mofid versus Agah responses change based on `days`, and Agah history is limited to the total-index series.

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 front-loaded and appropriately sized for a multi-source index tool. It is mostly efficient, with a slightly dense middle sentence explaining source behavior and Agah series limitations.

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 read-only tool with no output schema, the description is complete enough: it lists the index-card data, explains daily history behavior, describes source-dependent responses, and routes the agent to correct sibling tools.

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%, so baseline is 3. The description adds meaningful interaction semantics beyond the schema by explaining that `days` changes which source answers and what history is returned.

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 states a specific verb and resource: 'Show a market index' and 'its daily history.' It also names how it differs from siblings, explicitly routing sector indices to br_industries and today's snapshot to br_market.

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?

It gives clear conditional usage: without `days` only Mofid answers with the index card, while with `days` Mofid adds daily candles and Agah returns its total-index series. It also names alternatives for sector indices and today's snapshot.

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