godot_get_input_actions

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

The description only says 'Query all configured...' but does not disclose the optional filter parameter that affects the result set, nor does it describe the output format or any side effects. It does not add behavioral detail beyond the readOnlyHint annotation, and the claim of 'all' is slightly misleading given the filter option.

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, clear sentence that starts with the action verb. It is concise and front-loaded, with no unnecessary words.

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?

The description is minimal and does not mention the optional filter, the expected output, or any usage context. It omits key information that an agent would need to fully understand the tool's capabilities and limitations, relying solely on the schema for parameter 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?

The description does not explain the 'params' parameter or the 'filter_prefix' option; the schema itself provides the description for filter_prefix. Since the schema covers the parameter semantics, the description adds no additional meaning, but it does not contradict it.

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 queries all configured project input actions and key bindings, using the specific verb 'Query' and resource 'project input actions and key bindings'. This distinguishes it from sibling tools like godot_configure_input_action, which is for configuration, and other read tools.

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 provide any guidance on when to use this tool versus alternatives. It does not mention filtering, read-only nature, or any context where it would be preferred over other tools. The sibling list includes a configuration tool, but no comparative usage is stated.

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