call_native

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

With no annotations, the description carries full burden. It discloses that it resolves to verified canonical hash, refuses unknown/guessed hashes to prevent crashes, works on Legacy+Enhanced, and that entity/ped/vehicle args are handles (ints). Could be improved by mentioning if there are rate limits or side effects, but covers critical traits.

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?

Well-structured with clear paragraphs, bullet-like points for args, and concise. Every sentence adds value without redundancy.

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?

Given the tool's complexity (game modding, 6700+ natives), the description covers how to use, how to discover natives, safety info, and references companion tools. Output schema exists so no need to document return values.

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 0%, so description must compensate fully. It explains name with examples, args as ordered with type hints (handles for entities/ped/vehicle) and a pointer to PLAYER_PED_ID, and return_type as optional override with enum of types. This adds significant meaning beyond the bare 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 clearly states it calls a GTA V native function by name and is 'the primary way to do ANYTHING in-game.' It differentiates from siblings like call_native_by_hash and search_natives, providing specific verb and resource.

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?

Explicitly mentions when to use this tool ('primary way to do ANYTHING') and directs to alternatives: search_natives() for discovery and native_info() for args. However, it does not explicitly state when not to use it.

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