HUD info

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

With no annotations provided, the description does not disclose behavioral traits. It merely lists features without stating whether the tool is read-only, if it modifies state, or any side effects.

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?

The description is very short but lacks essential information. It is not concise; it is underspecified. Every word should earn its place, but here the phrase does not convey meaningful semantics.

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 no output schema, no annotations, and a single undocumented parameter, the description fails to provide enough context for an AI agent to use the tool correctly. It does not describe return values, behavior, or parameter constraints.

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 input schema has one parameter 'instance' with no description. Schema coverage is 0%, and the tool description does not mention the parameter at all, leaving its purpose and usage completely unexplained.

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 lists 'Status bar Y position, status bar / HUD scale, alt HUD, crosshair' but does not specify whether the tool reads or writes these values. The title 'HUD info' suggests read-only, but the verb is missing, making the purpose vague. Sibling tool 'read_hud' likely overlaps and is not distinguished.

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 guidance on when to use this tool versus alternatives like 'read_hud', 'map_info', or 'viewport_info'. No context or prerequisites are given.

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