Single tool 'gm_resourcetool_validate' has critical definition gaps. Input schema shows only a 'ctx' parameter with type 'Context' and a vague description 'Optional context parameter', but no details on what Context is, what fields it contains, or what values are accepted. Tool description is generic and under-detailed. No output schema is documented in the visible code. The tool appears to be a thin wrapper around ResourceTool validation but the MCP interface lacks the specificity needed for LLM selection and parameter construction. Schema is essentially absent (only shows parameter name and type stub, no validation rules, constraints, or structure). Error handling and recovery guidance are not visible.

• Expand tool description to 80 - 150 chars: explain that this tool validates a GameMaker project configuration by running ResourceTool checks in an isolated copy (no side effects on the main project). State when to call it: 'Use this to catch configuration errors before committing or publishing.' Include what it returns: success status and a list of validation errors (if any).
• Define the 'ctx' parameter explicitly. If it's meant to be optional, make it truly optional (required=false) and document what happens when omitted. If it requires fields, enumerate them: e.g. 'Context object with optional fields: project_path (string, GameMaker project root), config (object with validation rules)' or 'null to use defaults'.
• Document the output schema as a JSON object with explicit fields: { 'valid': boolean, 'errors': [string], 'warnings': [string], 'checked_items': integer }. This lets LLMs know what to extract and how to interpret results.
• Add error handling guidance: 'If validation fails, errors will list specific issues (e.g., missing asset references, invalid configurations). Review errors and correct the project, then re-run.' Categorize errors as configuration fixable vs. environment setup required.
• Consider renaming to 'validate_gamemaker_project' or 'check_project_configuration' if the tool is part of a broader toolset, the current name is too tied to an internal component (ResourceTool) and obscures its purpose for LLMs.
• If the tool modifies state (even in a disposable copy), clarify: 'This tool is read-only, it does not modify the original project.' This prevents agents from avoiding it due to fear of side effects.

Inferred effective spec: 2026-07-28+.

• Relies on Logging (deprecated) - log to stderr or use OpenTelemetry