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

Annotations already cover the read-only, idempotent, non-destructive, closed-world profile, so the bar is lower and the description still adds real value: it discloses data provenance (drop chances computed from cfgspawnabletypes.xml and cfgrandompresets.xml), that drop probabilities are map-dependent, and that ambiguous queries return a list rather than a single record.

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?

Front-loaded with the resource being described and the payload it returns, then the query mechanics, then the multi-match note. It is dense and every clause adds information, though the opening sentence is long enough that a reader has to parse several comma-separated field groups.

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 no output schema, the description adequately enumerates the returned data so an agent knows what to expect, and covers the ambiguous-match case. Minor gaps remain around not-found behavior and the lang enum's exact effect, but nothing critical to invoking the tool 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?

With only 33% schema coverage, the description has to carry meaning, and it does: it explains that query accepts display names in any language or class names with a concrete example, and that map governs the drop-chance computation. The lang parameter is only partially covered (the description alludes to 'any language' but does not explain the lang enum's effect).

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+resource ('Stats of a DayZ infected type') and enumerates exactly what fields are returned: health per hit zone, damage multipliers, attack damage, bleed chance, movement speed, drop table, and spawn events. This clearly distinguishes it from siblings like get_item, search_items, and compare_weapons.

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 explains the accepted query forms ('display name in any language or by class name') and the multi-match fallback, which implies usage, but never states when to prefer this tool over get_item, where_to_find_item, or search_items. No explicit alternatives or exclusions are given.

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