Single tool 't_get' has critical definition gaps. Description is trivial (9 chars: 'Get a thing.'), far below the 10-char minimum and 194-char baseline. Parameter 'id' lacks description (null value visible in schema). Schema is present but incomplete, no type info for the parameter itself, only integer type at property level. Tool name is generic and non-specific (does not follow verb_noun pattern clearly, 'get' is good, but 'thing' is vague). No output schema documented. No error handling guidance. The tool appears to be a test fixture (source file is McpServerTests.cs), not a production tool, which explains the minimal effort.

• Expand tool description to 50 - 200 characters. Example: 'Retrieve a resource by its numeric ID. Returns the resource object with all fields. If not found, returns a 404 error, try searching first.'
• Add description to 'id' parameter. Example: 'The numeric ID of the resource to retrieve (1 - 999999).'
• Document the output schema. Example: 'Returns an object with fields: id (integer), name (string), created_at (ISO 8601 date), status (enum: active|inactive).'
• Rename tool to follow verb_noun pattern. Example: 'get_resource' or 'get_item' (depending on what the API actually returns).
• Add error handling guidance. Example: 'If the resource is not found, returns error code 404. Try search_resources() with a partial name to find the correct ID.'