Single tool 'slow_count' has a basic description but critically lacks parameter descriptions and output schema documentation. The input schema shows only type 'integer' with null description for parameter 'n'. No output schema is documented. The tool definition is inferred from FastMCP decorator usage rather than explicit registration with full metadata. This server falls well below production baselines: 100% of A+ tools have documented return types and parameter descriptions; this tool has neither.

• Add a non-empty description to parameter 'n': e.g., 'The target count (integer, 1 - 1000). Tool will count from 1 to n, sleeping 1 second between each count.'
• Document the return type and structure: 'Returns a string message indicating completion, e.g., "Finished counting to 3". Also reports progress via ctx.report_progress().'
• Expand tool description to 100 - 200 characters explaining purpose and use case: 'Slowly counts from 1 to n, reporting progress after each second. Useful for testing long-running operations and progress reporting in agents.'
• Add numeric constraints to parameter 'n': minimum 1, maximum 1000 (or appropriate limit). Document timeout behavior if count takes too long.
• Implement error handling: validate that n > 0, return actionable error if invalid (e.g., 'Invalid count: n must be a positive integer between 1 and 1000').