get_gov_bond_yields

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

No annotations are provided, so the description carries the full burden. It discloses the data source (doviz.com tahvil bülteni), which is useful provenance, but does not describe update frequency, freshness, units, or what happens on source unavailability. For a data-fetching tool with no annotations this leaves a meaningful gap.

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?

Two short sentences: the first defines what is returned, the second names the source. Nothing extraneous and the primary payload is front-loaded.

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?

A zero-parameter, no-output-schema tool so requirements are modest, but the description omits units, update cadence, and fallback behavior. Source attribution partially compensates but the definition is only minimally complete for an agent to trust the data.

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?

Zero parameters, so the baseline is 4. There are no parameters to document, and the description correctly implies a no-argument retrieval.

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 (döndürür/returns) and resources (10-year Turkish government bond yield and the benchmark/reference 2-year bond yield). The term 'gösterge' with parenthetical clarification (referans/2 yıllık) makes it distinguishable from generic bond-yield siblings.

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 explicit when-to-use guidance versus siblings like get_policy_rate or get_tcmb_snapshot. Usage is only implied by the resource name; the agent must infer that this is for Türkiye sovereign bond market yields.

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