Critical gaps across all dimensions. Tool definitions exist only in mcp.json with minimal metadata. No input schemas visible, only tool names and descriptions. Descriptions are generic (10-50 chars), lack context on WHEN to use each tool, and provide no guidance on parameters, return values, or error handling. No parameter documentation visible. No output schema documentation. All 7 tools are READ_ONLY but lack idempotent hints or permission declarations. Tool names follow verb_noun pattern (positive), but lack parameter-level detail needed for LLM reasoning. This server appears to be a thin wrapper around Atlassian Bitbucket API with minimal agent-optimization.

• Add complete JSON Schema input definitions for all tools. Each tool must declare required parameters, types (string, integer, boolean), constraints (enums, min/max, regex patterns), and descriptions. Example: bb_get_repository should require 'workspace' and 'repo_slug' as strings with descriptions explaining what they are.
• Expand tool descriptions to 100-200 characters. Include WHAT the tool does, WHEN to use it (vs similar tools), and key return fields. Example: 'Retrieve a specific Bitbucket repository by workspace and slug. Returns repository metadata including ID, name, description, and clone URLs. Use this after bb_list_repositories to get details on a specific repo.'
• Document output schemas for all tools. Specify which fields are returned (e.g., repository_id, name, description, links) and their types. Include IDs needed for downstream tool calls (e.g., bb_get_repository must return repo_id for use in bb_list_pull_requests).
• Add pagination support to list tools. Declare limit (default 20, max 100), offset/cursor, and total_count in responses. Example: 'bb_list_repositories accepts limit (1-100, default 20) and offset (0+). Returns up to limit repos plus total_count for pagination.'
• Add tool annotations and permission declarations. Mark all tools with readOnlyHint=true and idempotentHint=true. Declare required scopes (e.g., 'read:repositories', 'read:pull_requests') so agents understand least-privilege configuration.