EVDS başlıca göstergeler (kod bilmeden)

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

Beyond the readOnlyHint annotation, the description discloses the response contents (latest value, date, series code, formula), the default date range, the EVDS limit of 150 observations, and the EVDS_API_KEY requirement. This is substantial behavioral context that helps the agent set expectations.

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 dense and front-loaded with the indicator list, and every sentence adds useful information. The bilingual repetition is slightly redundant but does not obscure the meaning.

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?

The description is complete for a simple read-only lookup tool: it covers selection, defaults, limits, auth, and response contents. With an output schema present and no nested complexity, nothing essential 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 schema already documents all three parameters with full coverage and an enum for gosterge. The description repeats the enum values and adds the 'by name' framing, but does not need to compensate for any schema gap, so the baseline 3 is appropriate.

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 states the tool returns Turkey's headline economic indicators by name, without requiring a series code. It lists the exact indicators and explicitly distinguishes itself from the EVDS code-based sibling tools.

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 phrase 'seri kodu bilmeden, adıyla' makes clear this is the tool to use for common indicators when the user does not know EVDS series codes. It does not explicitly name an alternative tool, but the usage context is clear and the sibling tools make the intended contrast obvious.

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