karar_denetim_defteri

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

No annotations are provided, so the description carries the full burden of behavioral disclosure. It states that the tool audits and produces a score, but it does not disclose whether it is read-only, whether it uses only the provided JSON, whether any data is stored or sent externally, or what side effects (if any) exist. For an analytic tool, this is sparse.

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 a single sentence with no fluff or repetition of the tool name. It front-loads the core action and outcome. However, it is so terse that it omits operational details, which is a minor structural weakness, but it remains appropriately compact.

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 one parameter, no annotations, and no explanation of the input format, the description is incomplete for an agent to invoke the tool correctly. The output schema exists, but the description still does not cover the decision-history input or how to interpret the calibration score. Sibling tools do not clarify this tool's boundaries.

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 only parameter, islem_gecmisi_json, has zero schema description coverage and the description never mentions it. The phrase 'geçmiş yatırım kararları' hints at the intended content, but the expected JSON structure, format, and how the parameter is used to generate the calibration score are completely unexplained.

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 uses a specific verb ('denetle' = audit) and names the resource ('geçmiş yatırım kararları' = past investment decisions) and the output ('kalibrasyon skoru' = calibration score). The 'Verdict Matrisi' detail differentiates this tool from sibling tools like sapma_analizi_raporu, making its purpose unambiguous.

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 description implies the tool is for auditing past investment decisions, but it does not explicitly state when to use it versus alternatives, nor does it mention exclusions or compare with related sibling tools such as sapma_analizi_raporu or portfoy_risk_analizi. Usage context is only implied through the purpose statement.

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