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

With no annotations, the description carries the full load. It does disclose two useful behavioral facts: the operation is a read ('listeler') and it spends no credits ('Kredi harcamaz') — meaningful given a credit-checking sibling. However, it says nothing about pagination, ordering, or what happens when no reports exist.

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, front-loaded with the action and scope, then the credit note. 'ayrıntılarıyla' (in detail) is mild filler but conveys report granularity, so almost nothing is wasted.

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 zero-parameter read tool with no output schema, the description covers what it returns (scan reports), the state filter (live/completed), and the cost profile. Missing details — pagination, result ordering, and the empty-list case — are modest gaps rather than blockers.

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 tool takes zero parameters, so the baseline is 4. Nothing in the description needs to explain parameter meaning, and it does not misrepresent the schema.

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 gives a specific verb and resource ('listeler' / lists, 'MCP tarama raporları' / MCP scan reports) plus scope ('canlı ve tamamlanmış' – live and completed, 'Hesabınıza ait' – belonging to your account). That is enough to separate it from siblings like vulkill_start_scan or vulkill_check_credits, though it does not explicitly name a sibling.

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?

Usage is only implied: it is the report-listing tool, so an agent should use it when it wants results. There is no explicit statement of when to prefer it over anything else, no prerequisites (e.g. must a scan have finished?), and no exclusions.

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