PostGrid MCP has 3 tools with basic schemas and descriptions. All tools are READ_ONLY and properly registered with Zod schemas. However, descriptions are minimal (10-100 chars, below the 194-char baseline), parameter descriptions are sparse or missing, and output schemas are not documented. Error handling returns structured responses but lacks recovery guidance. Tool naming follows verb_noun convention (postgrid_*) but is somewhat generic. No tool annotations present.

• Expand tool descriptions to 100-200 chars. For postgrid_list_sub_orgs, add: 'Retrieve all child partner organizations under the current account. Returns organization IDs, names, and creation dates. Use this to identify which sub-orgs to sample in postgrid_schema_probe.'
• Document output schemas explicitly. Add a comment block above each tool showing the response structure, e.g., '// Returns: { reachable: boolean, environment: string, sub_org_total: number, note: string }'
• Add descriptions to all parameters. For only_org in postgrid_schema_probe: 'Optional organization ID to limit sampling to. If omitted, samples parent org and up to 3 child orgs. Must be a valid sub-org ID from postgrid_list_sub_orgs.'
• Enhance error messages with recovery hints. Instead of 'ERROR: Invalid org ID', return 'ERROR: Organization ID not found. Call postgrid_list_sub_orgs() to see valid IDs.'
• Add tool annotations (readOnlyHint) to signal to clients that all three tools are safe to call without user confirmation. Use @modelcontextprotocol/server's tool annotation support.