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

Annotations already declare readOnlyHint=true and openWorldHint=true, so the safety profile is covered. The description adds genuinely useful context the annotations lack: a paid subscription tier is required (upstream data source dependency implied by 'kaynak bağlanınca dolar'). It says nothing about pagination, rate limits, or what happens when the paid tier is absent.

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 text is short and front-loads the resource, but the first line simply restates the tool title verbatim, so a chunk of the content is duplicated structured data rather than added meaning. The endpoint and paid-tier note are the only substantive additions.

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 tool with an unconstrained string parameter, no output schema, and no described response shape, the description is too thin: it never says what a returned record contains or what 'kaynak bağlanınca dolar' means for the caller. The paid-tier warning is the sole completeness gain over the schema and annotations.

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 description coverage is 0% for two parameters, so the description carries the full burden and does not meet it: 'gun' (day count, default 30, max 3660) and especially 'tur' (default 'gram', no enum, no description) are left completely unexplained. The word 'günlük' hints at daily granularity but does not clarify which values 'tur' accepts or how it relates to the sibling altin tool's type parameter.

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 names a specific resource and scope: historical gold prices at daily granularity, backed by the endpoint GET /v1/altin/gecmis. It separates itself from the current-price sibling altin only implicitly through the word 'gecmis' (history), without ever naming altin as the alternative.

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?

There is no guidance on when to call this versus altin (current prices) or doviz_gecmis (currency history); the agent must infer the distinction from tool names. The only usage-adjacent note is that a paid package is required, which is a precondition rather than a when-to-use rule.

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