godot_get_autoloads

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

The description states it queries autoloads, and the readOnlyHint annotation indicates no side effects. It does not specify return format or error behavior, but annotations already cover safety, so it is reasonably transparent.

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 with no extra words, directly stating the tool's action and resource.

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 is a simple read-only query with no parameters, the description is complete. An output schema exists for return values, so no need to explain them. Slight lack of mention of dependencies or non-read-only behavior is mitigated by annotations.

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 is empty (no parameters). Schema coverage is 100% (nothing to cover), so baseline is 3. The description adds no parameter details because none exist, which is acceptable.

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 'Query' and clearly states the resource 'all registered Autoload singletons'. It distinguishes from sibling tools like godot_set_autoload by its read-only intent.

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 does not explicitly mention when to use this tool versus alternatives (e.g., godot_set_autoload). It relies on the tool name and intent, but lacks explicit guidance on selection conditions.

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