EVDS seri verisi

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

Beyond the readOnlyHint/openWorldHint annotations, the description discloses a notable truncation behavior — at most 150 observations counted back from the end — plus the need to paginate for longer ranges, the 365-day default window, and the EVDS_API_KEY requirement. These are exactly the behavioral quirks annotations do not convey.

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?

Purpose is front-loaded and every clause earns its place — examples, limit, default, and auth are all load-bearing. The Turkish/English repetition of the core purpose is mildly redundant but acceptable for a mixed-language audience.

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 and annotations covering the safety profile, the description covers the remaining operational essentials: auth, result limit, default range, and pagination strategy. The only notable gap is not clarifying how evds_seri differs from evds_seriler for an agent deciding which to call.

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% with rich per-parameter descriptions, so the baseline is 3. The description adds real-world value: concrete series codes (TP.DK.USD.S.YTL, TP.DK.EUR.S.YTL, TP.TUKFIY2025.GENEL) and a mapping hint (formul=3 gives yıllık enflasyon %), giving the agent ready-to-use parameter combinations.

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?

States a specific resource and action: fetching observations of one or more series from TCMB EVDS ('bir ya da birkaç serinin gözlemleri'). The example codes and 'Time-series observations' reinforce the data-retrieval purpose, clearly distinguishing it from siblings like evds_kategoriler (categories) and evds_seriler (series metadata).

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 operational guidance (150-observation cap, pagination advice, default 365-day range) but never says when to prefer evds_seri over the near-namesake evds_seriler or evds_gosterge. An agent must infer usage from the broader EVDS sibling group rather than being explicitly routed.

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