evds_categories

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

With no annotations, the description must carry the burden. It discloses the scope (main categories) and gives examples, but does not mention any additional behaviors like pagination, language handling nuances, or read-only assurance. For a simple listing tool, 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, uses examples to clarify scope, and includes the parameter explanation in two brief lines. Every word 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?

The tool is simple with one optional parameter and an output schema. The description explains purpose and parameter semantics. The examples and scope are sufficient for an agent to correctly invoke it, though it does not mention any limitations or edge cases.

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 lacks descriptions (0% coverage). The description compensates by explicitly stating 'lang: 'TR' or 'ENG'', providing allowed values that are not in the schema. This adds significant meaning beyond the schema.

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 it lists TCMB EVDS main categories, with specific examples (exchange rates, interest rates, inflation). This is a specific verb+resource+scope. However, it does not explicitly distinguish it from sibling tools like evds_datagroups, though the term 'main categories' gives implicit differentiation.

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 usage is implied: the tool is for listing main EVDS categories. There is no explicit mention of when to use this vs. alternatives such as evds_datagroups, nor any exclusions. The example categories give some context, but no direct guidance is provided.

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