get_market_summary

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

No annotations are provided, so the description carries the full behavioral burden. It discloses only that the data is 'anlık' (instant/real-time), implying a read-only live snapshot, but says nothing about refresh cadence, data source, authentication, or failure behavior. For a tool with zero annotation coverage this is thin.

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?

A single, front-loaded sentence that names the exchange, the indices, and the payload types with no filler. It is efficient, though the parenthetical stock categories are slightly loose phrasing rather than a crisp scope statement.

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 no input parameters and no output schema, the description sensibly enumerates what the response contains (index levels plus notable stock prices and changes). That is close to complete for a trivial no-arg read tool; only the routing versus sibling index tools is missing.

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 tool takes zero parameters, which is the baseline-4 case. The description correctly implies a no-argument call by describing a fixed set of indices and stock categories rather than any filterable input.

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 (Borsa İstanbul market summary) and enumerates its contents: XU100/XU030/XU050 indices plus key banking and industrial stocks with current price and change. That is a clear verb+resource statement an agent can act on. It does not, however, distinguish itself from siblings like get_bist_indices or get_bist_price, which plausibly overlap.

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?

There is no guidance on when to choose this summary over get_bist_indices, get_bist_price, or get_market_movers. The reader must infer that this is a broad snapshot rather than a per-symbol lookup. No exclusions, prerequisites, or alternatives are stated.

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