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

Annotations already declare readOnlyHint=true and openWorldHint=true, and the description adds genuinely non-obvious behavioral context beyond them: a per-call price of $0.002 USDC, the x402 payment rail (Base, Solana, Arc), and the fact that failed calls are not charged. That billing/auth detail is exactly what an agent needs before invoking a paid endpoint, though rate limits and data freshness/lag are not stated.

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?

Front-loaded with what the data is and its scope, then a single dense field inventory, then pricing. The long field list is functional rather than filler because it tells the agent what questions this dataset can answer; no sentence restates the title.

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?

With an output schema present, the field enumeration is technically redundant but harmless, and the annotations plus the explicit cost/auth model cover the safety and payment dimensions. What is missing is freshness (as-of/EOD timing) and whether pagination terminates at 100 pages, though the count field mentioned helps.

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 description coverage is 100%, so the three parameters are already documented, and the schema itself lists the same examples (Shares, Bonds, Warrant, ETF) that the description repeats for the 'type' filter. The description adds only the ordering/paging convention ('30 securities per page in TASE's order'), which slightly informs but does not exceed the schema.

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 names a specific resource (Tel Aviv Stock Exchange end-of-day data) and enumerates the exact fields returned (ISIN, symbol, last price, turnover in ILS thousands, bond details, etc.), which unambiguously separates it from every crypto and non-TASE finance sibling. An agent can identify this as the only TASE equities/bonds dataset without opening the schema.

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?

Usage is only implied: it is clear you call this for TASE end-of-day listings, but there is no explicit when-to-use/when-not-to-use statement and no named alternative (e.g. for intraday or other exchanges). The pagination detail ('30 securities per page in TASE's order') gives partial context on how to iterate but not on tool selection.

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