search_series

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

With no annotations, the description carries the full burden and does well: it discloses the EVDS_API_KEY requirement and, notably, the degraded keyless mode limited to FX series. It also names the returned fields, though it omits result ordering, pagination, or what happens on an empty match.

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?

Three tight sentences: purpose, requirement, return/next-step, and the keyless caveat. The essential routing information is front-loaded with no filler.

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?

An output schema exists, so return values need not be explained in detail, and the auth/degradation behavior is covered. The only gap is the undocumented 'limit' parameter, which an agent must infer from the schema alone.

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 50%: the 'query' parameter is documented in the schema, and the description usefully adds that keywords may be Turkish or English. The 'limit' parameter (default 10, max 50) is left unexplained in both the schema and the description, so the description only partially compensates.

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 verb+resource ('Find EVDS series codes') and immediately distinguishes itself from the sibling get_series, which consumes the codes it returns. An agent can tell exactly what this tool produces without opening a schema.

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?

Explicitly routes the agent forward: 'pass a code to get_series', and states the authentication prerequisite plus the fallback behavior when no key is present. It does not spell out when-not-to-use (e.g. versus list_data_sources), but the usage context is clear.

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