AegisTrace is a CLI-only workflow tool with 8 commands exposed as tools. All tools have descriptions (10-80 chars, mostly adequate) and input schemas with typed parameters. However, schemas lack depth: no enums for constrained values, minimal parameter descriptions (many under 20 chars), no output schemas documented, and no error recovery guidance. Tool names are verb-based (compile, verify, run) but descriptions are terse and lack WHEN/WHY context. No tool annotations (readOnlyHint/destructiveHint). Composition is reasonable (single responsibility per tool), but parameter documentation is sparse. Average tool score: 42/100.

• Add output schemas to all tools. Document what compile returns (e.g. {artifact_path, digest, step_count, edge_count}), what run returns (result, execution_time, journal_path), etc.
• Expand parameter descriptions to 50-100 chars. For 'event' param: 'Event index in journal (0-based integer, or -1 to inspect all events)'. For 'approve': 'Auto-approve guarded workflow steps that require manual confirmation (boolean).'
• Add error recovery hints to tool descriptions. E.g. compile: 'If YAML parsing fails, check syntax with a YAML validator. If verification fails, inspect the workflow structure with verify command.'
• Annotate tools with readOnlyHint/destructiveHint. Mark verify, inspect, replay, verify-proof as read-only. Mark run, keygen as destructive (write/create side effects).
• Document default values and constraints. E.g. 'output defaults to workflow_file + .aegis', 'journal defaults to run.atlog', 'event must be >= -1'.