Rig Constellation exposes 36 tools for code graph navigation and manipulation. Only 6 tools have visible input schemas in the source (rig_callers, rig_deps, rig_files, rig_neighbors, rig_node, rig_search); the remaining 30 are defined in .contracts/tools/*.contract.ts files that are not provided. Of the 6 visible tools, only rig_search has a substantive description (>20 chars). Tool names follow verb_noun convention (rig_add_*, rig_list_*) but lack clarity on domain boundaries, e.g., rig_explore, rig_drill, rig_chain are vague. No visible error handling guidance, no output schema documentation, and no parameter descriptions for most tools. The contract system suggests structured definitions exist, but without access to the contract files, schemas cannot be verified. Conservative scoring reflects inability to audit 83% of tool definitions.

• Publish all .contracts/tools/*.contract.ts files in the repository root or docs/ so tool definitions can be audited. Contract system is sound but opaque to external reviewers.
• Add substantive descriptions (50 - 200 chars) to all 30 contract-defined tools. Current descriptions are missing or inferred from names alone. Example: 'rig_explore' → 'Traverse the code graph from a given anchor, returning connected nodes up to depth N. Use to discover related functions, classes, and dependencies.'
• Document output schemas for all tools. Include field names, types, and whether results are paginated. Example for rig_search: 'Returns array of {id, name, kind, file_path, score}. Limit 20 results; use offset for pagination.'
• Add parameter descriptions to rig_callers, rig_deps, rig_files, rig_neighbors, rig_node. Example: 'id (string, required): The anchor ID (function, class, or file). Obtain via rig_search or rig_node.'
• Rename vague tools to action-verb form: rig_explore → rig_traverse_graph, rig_drill → rig_analyze_depth, rig_cold → rig_find_cold_code, rig_focus → rig_set_focus. Clarify what each does in one word.