Get GDevelop preview status

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

Annotations already declare readOnlyHint=true and openWorldHint=false, and the description adds valuable behavioral context: the tool returns either a single session (when previewId is provided) or all sessions (when omitted). This conditional behavior is not captured by annotations alone. However, it does not disclose error handling (e.g., invalid ID) or response format, which are minor gaps for a read-only tool.

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 a single, concise sentence that front-loads the purpose and includes the key conditional behavior. There is no redundancy or filler.

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 tool with one optional parameter and no output schema, this description is largely complete. It covers the core behavior (single vs. all sessions) and the read-only nature is reinforced by annotations. It does not specify the return format or edge cases, but these are not critical for a simple query tool.

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 provides no description for previewId (coverage 0%), so the description carries the burden. It explains the parameter's meaning and effect: 'when previewId is omitted' implies that previewId selects a single session, while omitting it lists all. This adds semantic meaning that the schema lacks, though it could be more explicit in naming the parameter.

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's function: 'Return one preview session, or list all sessions when previewId is omitted.' This uses a specific verb ('return'), defines the resource (preview session), and explains the conditional behavior. It effectively distinguishes itself from sibling tools like build_preview and stop_preview by indicating it is a read-only status query.

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 description implies usage but does not explicitly state when to use this tool versus alternatives. It says 'Return one preview session, or list all sessions when previewId is omitted,' which suggests it is for fetching status, but it does not provide context such as 'use after starting a preview' or compare to stop_preview. The usage is clear from the name and behavior but lacks explicit guidance.

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