gdscript_complete

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

Description adds significant context beyond readOnlyHint annotation: it reveals the completion engine, return format (candidate labels with kind and detail), and the critical scene-awareness behavior. No contradictions with annotations.

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?

Two sentences and an IMPORTANT note are highly concise and front-loaded. Every sentence adds value, with clear emphasis on critical usage details.

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 (4 parameters, no output schema), the description adequately covers return type, scene-awareness, and coordinate system. It compensates for the lack of output schema with explicit details.

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 100% with thorough descriptions for each parameter. The description reinforces zero-based coordinates but does not add meaning beyond the schema, so baseline score is appropriate.

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 valid completions at a cursor position using Godot's completion engine. It distinguishes itself as the only scene-aware query, contrasting with sibling tools that do not have this capability.

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 explicitly notes zero-based coordinate requirements and frames the tool as the only scene-aware option, guiding when to use it over other completion or analysis tools. It does not explicitly list exclusions but context is clear.

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