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

Annotations already declare readOnlyHint=true, destructiveHint=false and openWorldHint=false, so the safety profile is covered. The description adds domain-specific reassurance that matters here — no scan is launched and no credits are consumed — plus per-query return behavior, which goes beyond the annotations. The fragment 'Modlar 3 yetki beyanından ayrıdır' is too terse to convey what the agent should infer.

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?

Five short clauses, front-loaded with the scope then the query behaviour then the exclusions; nothing is padded. The single opaque sentence about modes versus permission declarations is the only sentence that does not clearly earn its place.

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 one-parameter, read-only lookup with no output schema, the description covers what to pass, what each query returns and what the tool will not do. The absence of an output schema leaves the response shape only loosely implied, but nothing an agent needs in order to call it correctly is missing.

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 coverage is 100%, so the baseline is 3, and the schema definition largely duplicates the description's enumeration of query values. The description does add one behaviour the schema omits: an empty query returns a summary rather than an error, which is genuinely useful. Beyond that it repeats the schema's examples (VK-001, SQL, CWE-89) rather than adding new semantics.

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 states a concrete scope: 12 security domains, the 260-control catalogue and the 5 scan modes, and the verb 'açıklar' (explains) makes clear this is a reference/lookup tool rather than a scanner. It never names a sibling, but the closing sentence 'Tarama başlatmaz, kredi harcamaz' functionally separates it from vulkill_start_scan and vulkill_auto_scan.

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?

It enumerates the usage cases precisely: empty query for a summary, query=all for the full 260-item list, a mode name for mode scope, and an ID/CVE/CWE for targeted matches. It also redirects the agent elsewhere for executed checks ('Çalıştırılan kontroller için görev raporunu okuyun') and excludes scan execution and credit spending, though it does not name the alternative tools explicitly.

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