Two tools with minimal schema rigor and incomplete descriptions. tapac_find_contacts has a reasonable schema with enums and ranges, but the description is vague about return structure and lacks actionable guidance. tapac_status has no input schema (empty object) and a trivial 10-word description. Neither tool documents output format, pagination, or error recovery. The Python implementation shows placeholder behavior (returns instructional text, not actual API calls), suggesting the tools are not yet functional. No tool annotations, no structured output documentation, no error classification.

• Add a complete output schema for tapac_find_contacts: document that it returns an array of contact objects with fields {name: string, title: string, company: string, email: string, source: string, verification_status: 'verified'|'unverified'|'invalid'}, and include pagination (total_count, next_cursor).
• Expand tapac_status description to 50+ chars explaining what 'active' means and what the user should do if the key is not set. Current description is 10 words.
• Add input schema to tapac_status (currently empty {}). Even a status check should document that it accepts no parameters explicitly.
• Implement actual API calls in the Python server instead of returning placeholder text. The current implementation is a stub that does not invoke the TAPAC backend.
• Add error classification to tapac_find_contacts: distinguish between 'API key missing' (user-fixable), 'rate limit exceeded' (retryable), and 'invalid criteria' (user-fixable with guidance on valid industries/locations).