get_player_info

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

No annotations provided. Description does not mention side effects, permissions, failure conditions (e.g., if not in an aircraft), or whether the data is real-time. For a read-only tool, basic safety assumptions are missing.

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?

Single sentence is efficient and front-loaded with the main verb and resource. No fluff, but could benefit from a slightly more structured format (e.g., bullet points for the listed fields).

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?

No output schema, so description partially compensates by listing return fields. However, it lacks details on data format, unit of measurement, or preconditions (e.g., player must be in an aircraft). Adequate for a simple tool but incomplete.

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?

No parameters exist, so schema coverage is 100%. Description adds value by enumerating the returned fields (position, altitude, etc.), which is beyond 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 clearly states the tool retrieves specific information about the player's aircraft (position, altitude, speed, heading, fuel). It distinguishes from siblings like get_aircraft_list (lists all aircraft) and get_all_units (all units).

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?

No explicit when-to-use or alternatives are given. The description implies it's for the player's current aircraft, but does not differentiate from get_aircraft_list or get_mission_info for similar purposes.

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