Server has 5 tools with basic verb-noun naming (list_, get_, create_). All tools have descriptions (10-100 chars), but most are minimal and lack actionable context. Input schemas are present for all tools with type declarations, but parameter descriptions are sparse or missing. Output schemas are undocumented, tools return strings or dicts without specifying structure. Error handling is minimal (generic 'Failed to fetch' messages). No pagination, no field-level guidance, no recovery hints. The create_new_post tool is untested and returns a dict instead of a string, creating inconsistency. Overall: functional but well below production baseline (194 char avg description, 100% param descriptions in A+ tools).

• Document output schemas for all tools. E.g., list_publications returns {publications: [{id: string, name: string}]}. Specify field types and meanings so LLMs can chain calls.
• Expand parameter descriptions to 50-100 chars with format hints. E.g., publication_id: 'UUID of the publication (format: pub_xxxxxxxx-xxxx-xxxx-xxxx-xxxxxxxxxxxx)'.
• Rewrite tool descriptions to 100-150 chars, including WHEN to use and WHAT it returns. E.g., 'List up to 5 recent confirmed posts for a publication, ordered by publish date descending. Returns post IDs and titles for further retrieval.'
• Add actionable error messages with recovery hints. E.g., 'Publication not found. Call list_publications() to see available IDs.' instead of 'Failed to fetch publications.'
• Make create_new_post return consistent string format and document that it requires enterprise API access. Add a note in the description: 'Requires enterprise-tier API key. Returns post ID and web URL on success.'