Three simple tools with basic descriptions and schemas. All tools have descriptions (10-60 chars, below the 194-char baseline) and input schemas with typed parameters. However, descriptions lack depth, they state WHAT but not WHEN or WHY to use each tool. No output schemas documented. No error handling guidance. No parameter constraints (enums, ranges). Tools are trivial (echo, reverse, add) and do not reflect production patterns like pagination, chaining IDs, or recovery guidance. Naming is clear (verb_noun) but tools lack the sophistication expected in production agents.

• Expand descriptions to 100-200 chars. Include WHEN to use each tool and any prerequisites. E.g., 'Echo a message back unchanged to verify server connectivity. Use this as a health check before calling other tools.'
• Document output schemas explicitly. E.g., for 'add': 'Returns an object {result: integer, a: integer, b: integer, timestamp: ISO8601}' so LLMs know what fields to expect.
• Add error handling guidance. E.g., for 'add': 'If integers overflow, returns error: "Sum exceeds max integer. Try smaller values."'
• Add parameter constraints in descriptions. E.g., for 'add': 'a and b must be integers in range [-2147483648, 2147483647].'
• Replace trivial examples with realistic production tools (e.g., search_users, create_ticket, send_email) that demonstrate pagination, chaining IDs, and error recovery patterns.