Two tools with minimal definitions. Both have basic descriptions (under 100 chars) and simple string-only schemas. No parameter validation, no error handling guidance, no output schema documentation, no tool annotations. Naming is generic ('welcome-tool', 'echo-tool'), lacks action verbs. No composition or chaining support. Descriptions are too brief to guide LLM selection effectively.

• Rename tools with action verbs: 'welcome-tool' → 'greet_user', 'echo-tool' → 'echo_message'. Follow verb_noun convention from production baselines.
• Expand descriptions to 150 - 250 chars. Include WHAT the tool does, WHEN to use it, and what it returns. Example: 'greet_user: Generates a personalized greeting message for a user. Use this to welcome new users or start friendly interactions. Returns a greeting string.'
• Document output schema explicitly. Add a 'returns' field describing the response type and structure. Example: 'Returns: {type: string, description: "Greeting message"}'
• Add input validation and error messages. If 'name' is empty, return 'Error: name parameter required. Provide a non-empty string.' instead of silently defaulting to 'friend'.
• Add tool annotations to schema. Set 'readOnlyHint: true' for both tools so agents know they are safe to call without side effects.