get_fon_fiyat_gecmisi

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

With no annotations provided, the description must fully convey behavior. It states the tool returns daily price history, but omits details like whether it is read-only, rate limits, response format, or error handling. This is minimal disclosure.

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 extremely concise: a single sentence for purpose followed by a clear Args section. Every word is necessary, and the structure is front-loaded with the main function.

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 covers the tool's purpose and parameters adequately. However, it lacks details on output format, error states, or prerequisites (e.g., valid fund code). For a simple historical query, it is sufficient but not fully complete.

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 description adds significant value by explaining fon_kodu as 'TEFAS fon kodu' and listing exact allowed values for periyod. This compensates for the 0% schema description coverage in the input 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 returns the fund's daily price history (Fonun günlük fiyat geçmişini döner), matching the tool name. However, it does not explicitly distinguish itself from sibling tools like get_fon_fiyat (current price) or get_fon_portfoy (portfolio), though the resource is distinct.

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?

No guidance on when to use this tool versus siblings such as get_fon_fiyat or karsilastir_fonlar. The description implies usage for historical data, but there are no explicit conditions or alternatives mentioned.

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