Automagik Hive exposes 12 tools with critically insufficient definition quality. While tool names follow action-verb conventions (python_executor, web_search, file_reader), the implementations lack essential schema documentation, parameter descriptions, and output specifications. Source code inspection reveals that tools are registered in hive/config/builtin_tools.py, but input schemas are minimal, most contain only basic string/integer/boolean types without constraints, enums, ranges, or detailed descriptions. Tool descriptions themselves are brief (5 - 20 words) and lack context about when to use each tool, what it modifies, dependencies, or error recovery. Most critically, there is NO EVIDENCE of documented output schemas, pagination, or error handling guidance. The rubric requires that tools returning lists offer pagination and limits; none do. For a server exposing destructive tools (python_executor, shell_tools, sql_query, delete operations), absence of confirmation patterns, dry-run modes, or permission checks is a critical gap. Security-critical parameters (API keys, credentials) appear to be handled externally, but the tool definitions do not declare what permissions each requires, blocking least-privilege verification.

• Add documented output schemas for every tool. Include field names, types, and constraints. For tools returning objects, show the full structure. For lists, specify max items, pagination fields, and total count.
• Expand tool descriptions to 50 - 150 characters following the pattern: 'What it does, when to call it, what it returns.' Example: 'Execute Python code safely in an isolated sandbox. Use for data processing, math, or testing logic. Returns output, any errors, and execution time.'
• Add detailed parameter descriptions with format/constraint rules. For 'file_path': 'Path to file to read (must be under /data/, no ../ traversal, max 255 chars, supports .txt, .csv, .json, .yaml).' For enums, replace prose with a declared enum list.
• Declare input constraints (min/max for numbers, regex/length for strings, enum lists). Replace 'optional' with defaults; state 'defaults to 20' not 'optional max_results'.
• Add permission declarations to every tool. Specify what scopes are required (e.g., 'Requires: read:email' or 'Requires: write:github.repo'). Gate destructive tools behind explicit permission checks.
• For tools modifying state (python_executor, sql_query, shell_tools, github_api, slack_api, email_tools), add a 'dry_run' boolean parameter (default true) so agents can preview side effects before committing.
• Restructure github_api and slack_api away from a generic 'action' string parameter. Instead, expose separate tools: create_github_pr, list_github_issues, send_slack_message, etc. Each tool does one thing clearly.