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

Annotations declare readOnlyHint=true/openWorldHint=false, and the description reinforces this with a strong no-side-effect guarantee ('Hiçbir şey göndermez') plus a data-handling constraint ('Hassas kişisel veri ... eklemeyin') and the output artifacts produced. It does not, however, specify the mailto format or the draft's structure, so it adds real value without being exhaustive.

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 tight sentences, each doing distinct work: what is produced, what must not happen (sending), and a privacy constraint. The no-send statement is slightly redundant against readOnlyHint, but the phrasing is front-loaded and waste-free.

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 5-parameter, 0-required tool with no output schema, the description usefully names the artifacts returned (draft + mailto link) and the safety profile. The remaining gap is that half the optional inputs (ad, proje, tercih) are never contextualized, which an agent may need to fill them sensibly.

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 only 40%: konu and ozet carry descriptions, while ad, proje and tercih (beyond its self-evident enum) are undocumented. The description contributes no parameter-level semantics at all, so it fails to compensate for the coverage gap as the low-coverage rule requires.

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?

Names a specific verb and artifact set (e-posta taslağı ve mailto bağlantısı) for a clearly delimited resource — a consultation-request draft. It is plainly distinct from the sibling read/assessment tools (buro_bilgisi, kontrol_listesi_getir, on_degerlendirme_yap) without needing their schemas.

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?

States the triggering condition ('Kullanıcı büroya danışmak istediğinde') and the required follow-through workflow ('taslağı kullanıcıya gösterin, kullanıcı kendi e-posta uygulamasından gönderir'). No sibling is named as an explicit alternative, so it stops just short of a 5.

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