EVDS veri grupları (bir kategoride)

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

With readOnlyHint and openWorldHint already present, the description adds relevant context: an API key is required and the tool operates on a single EVDS category rather than the whole dataset. No contradiction with annotations, though failure behavior for invalid category ids is not disclosed.

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 compact and front-loads the main purpose, with concrete examples and a clear next-step pointer. The English sentence partially duplicates the Turkish opening, but the overall size is appropriate and scannable.

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 simple one-parameter read tool with an output schema, the description covers what is returned, the required API key, the source of the input id, and the follow-up tool. Minor edge-case behavior is unspecified, but the agent has enough to invoke it correctly.

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 the schema already documents kategoriId as the id from the evds_kategoriler output. The description does not add meaningful parameter-level detail beyond that, so it stays at the baseline 3.

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 identifies a specific resource: data groups within one EVDS category, and lists the returned fields with concrete examples such as 'bie_dkdovytl = Döviz Kurları' and 'bie_tukfiy2025 = TÜFE 2025=100'. It is clear enough to distinguish from evds_kategoriler and evds_seriler, though it lacks an explicit verb like 'list' or 'get'.

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 gives useful workflow context: the kategoriId comes from evds_kategoriler output and the next step is evds_seriler. It also states the EVDS_API_KEY prerequisite. However, it does not explicitly say when not to use this tool versus its siblings.

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