get_level_info

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

With no annotations provided, the description carries the full burden of behavioral disclosure. It clearly identifies the operation as read-only ('Get information') and discloses the exact return structure ('level_name' and 'level_path' fields). It does not mention potential failure when no level is loaded, but this is a minor gap for a zero-parameter getter.

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 two compact sentences with no filler. The core purpose is front-loaded, and the return format is presented in a clear, structured way.

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 simple, zero-parameter, read-only tool with an output schema available, the description covers the essential purpose and return fields. It is complete enough for an agent to invoke the tool and interpret the result. The only minor omission is explicit error behavior when no level is loaded.

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 has zero parameters, so the 0-parameter baseline of 4 applies. The description correctly focuses on the output rather than inputs, since there are no parameters to document.

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 uses a specific verb ('Get') and resource ('currently loaded level'), making the tool's purpose immediately clear. It is easily distinguished from sibling tools like list_levels or load_level because it targets the current level rather than listing or loading. The mention of exact return fields adds precision.

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?

The phrase 'currently loaded level' provides clear context for when to use this tool, and the zero-parameter signature implies it is a simple getter. However, it does not explicitly state when not to use it or mention alternatives, leaving some differentiation to inference.

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