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

Annotations already declare readOnlyHint=true and openWorldHint=true, so safety is covered. The description adds genuinely new operational context: a paid-tier requirement and a cost of 2 request units per call, which matters for an agent managing quota. It stops short of describing response shape or how the 100-symbol cap behaves at the boundary.

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 short, front-loaded lines: what it returns, the endpoint, then the cost/auth caveats. Efficient, though the first line largely duplicates the tool title rather than adding information.

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?

With only two optional, fully documented parameters and no output schema, the tool is simple and the description covers cost and access tier. It nonetheless leaves open what happens with zero arguments (all symbols? all groups?) and how this differs from the asset-specific sibling tools, which is the main gap for correct 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?

Schema description coverage is 100% — `grup` carries its enum explanation and `sembol` explains the comma-separated format and 100-item limit — so the schema does the work. The description contributes nothing about the parameters, leaving the baseline 3 appropriate.

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 phrase 'Anlık fiyatlar (alış, satış, günlük değişim)' names the resource and the three fields returned, and the endpoint `GET /v1/piyasa/fiyat` confirms the surface. However, it provides no differentiation from siblings like `doviz`, `altin`, or `cevir_doviz`, which plausibly return overlapping price data, so an agent cannot tell from the description alone why it should pick this tool over those.

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 only usage-relevant statement is 'Ücretli paket gerekir' (paid package required), which is a prerequisite rather than a when-to-use rule. There is no guidance on when this bulk price endpoint should be chosen instead of the per-asset tools such as `doviz` or `altin`, and no note on behavior when no parameters are supplied.

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