evds_series_list

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

No annotations are provided, so the description carries the full transparency burden. It discloses that the tool lists all series and returns codes and start dates, which gives some behavioral insight. However, it does not mention pagination, rate limits, or any side effects (though 'List' implies read-only). This is adequate but not rich.

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 concise, front-loaded with the main action, and includes a clear argument list without unnecessary fluff. Every sentence earns its place.

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 listing tool, the description covers the essential purpose and arguments. An output schema exists, so return values are already documented externally. The missing pieces are minor caveats (e.g., pagination, sorting), but overall it is complete enough for proper selection and invocation.

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 descriptions coverage is 0%, so the description must compensate. It defines datagroup_code as 'Datagroup code from evds_datagroups (e.g. 'bie_dkdovytl')' and lang as ''TR' or 'ENG''. This adds meaningful context beyond the bare schema, though it could include more detail about expected formats or defaults.

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 uses a specific verb ('List') and clearly states the resource ('all series in an EVDS datagroup') and the output ('with codes and start dates'). It distinguishes itself from siblings like evds_search_series by emphasizing 'all series' in a datagroup.

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 clear context for when to use the tool: to list series in a datagroup. It also notes that the datagroup_code comes from evds_datagroups, implying a prerequisite. However, it does not explicitly mention alternatives or exclusions, so it falls short of a 5.

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