The Entra News MCP Server defines 4 well-structured tools with clear, specific names and good descriptions. All tools follow verb_noun naming convention (search_*, get_*, list_*, find_*). Descriptions are comprehensive (120-280 chars), explaining WHAT the tool does and WHEN to use it. Input schemas are present with typed parameters and mostly good descriptions. However, there are consistent gaps: (1) Required/optional parameter status is not always explicit in schema; (2) Output schemas are undocumented, responses are returned as formatted text strings rather than structured objects; (3) No error handling documentation visible; (4) No tool annotations (readOnlyHint, etc.) despite all tools being read-only. These are fixable gaps that prevent a higher score.

• Add explicit 'required' arrays to all tool schemas. E.g. for search_entra_news: 'required': ['query']. For get_issue: document that one of issue_number OR date must be provided, and validate this in the handler.
• Document output schemas as structured objects. Instead of returning formatted text strings, return JSON with typed fields: {results: [{title: string, date: string, url: string, ...}], total: number, nextOffset?: number}. Provide this schema in the tool description or a separate 'outputSchema' field if the MCP SDK supports it.
• Add tool annotations to the Tool definitions. For all 4 tools: set readOnlyHint: true in the Tool object. This signals to clients and LLMs that these tools do not modify state and are safe to call speculatively.
• Document error handling in each tool description. Add a sentence like: 'If the issue is not found, an error will be returned with available issue ranges. Call list_issues() to discover valid issues.' Similarly for search results with no matches.
• Add validation and specific error messages in the handler code (src/tools/*.ts). E.g. in handleGetIssue, if neither issue_number nor date is provided, return: 'Error: Must provide either issue_number (e.g. 42) or date (e.g. "2024-03" or "2024-03-15")'.
• For find_tool_mentions, clarify in the description that results may include synthetic content mentions (marked '📄 Content mention') in addition to tool entries. The code comments indicate this, but the tool description should make it explicit.
• Add pagination guidance to search_entra_news description: 'Results are limited to the specified limit parameter (max 50). If you need to explore a large result set, refine your query rather than relying on pagination; the tool returns the most relevant matches first.'