Pre-release token and context optimization skill for AI coding agents with tool-output externalization, evidence storage, and deferred tool discovery
Syntavra presents a specialized tool set for artifact externalization and tool discovery, but suffers from critical definition gaps. While tool names follow verb_noun patterns (externalize, verify, search, reveal, lineage), descriptions are inconsistent in depth and actionability. Most critically, input schemas are visible but lack comprehensive parameter descriptions, many parameters have minimal or generic descriptions (e.g., 'Artifact ID to verify' without format/constraint details). The tool set is domain-specific and internally coherent, but lacks the LLM-optimization guidance (format constraints, error recovery hints, dependency documentation) required for production agent use. No tool descriptions exceed 200 chars; several are under 50 chars. Parameter descriptions are sparse, 'Artifact ID', 'Search query', 'Segment index' lack context on valid formats, ranges, or how to obtain these values. Output schemas are not documented in the tool definitions provided.
Classify whether a query needs tools or can be answered from context
Describe MCP tool catalog with namespace/family summaries
Two-stage deterministic tool discovery with host capabilities and schema budget
Externalize tool output with exact-first local virtualization, search, reveal and lineage capabilities
Retrieve lineage chain for externalized artifact
Build namespace tree from tool descriptors
Reveal externalized artifact content with optional lens and byte budget
Search externalized artifact content by query string
Parameter descriptions lack actionable constraints. 'Artifact ID to verify' does not specify format (UUID, hash, opaque string), length, or how to obtain one. LLMs cannot infer valid values.
Output schemas not documented in tool definitions. LLMs cannot plan downstream calls or extract required fields (e.g., what does reveal() return? structured object or raw bytes?).
| Scored | Grade | Overall | Spec posture | Rubric |
|---|---|---|---|---|
| 2026-09-23 | F | 45 | 2026-07-28+ | v2 |
Search externalized artifact and return results as packed content
Generate Merkle proof for artifact segment
Get statistics about tool output externalization engine
Verify integrity of externalized artifact using exact handle
Tool descriptions are too brief (avg ~50 chars) and lack WHEN/WHY guidance. 'Retrieve lineage chain for externalized artifact' does not explain when an agent should call this vs other tools, or what lineage means in this context.
No error handling guidance. Tools do not document what errors are possible, whether they are retryable, or what the LLM should do next (e.g., 'Artifact not found, try search() first').
Parameter 'lens' in reveal() uses an enum-like constraint ('critical', 'full', etc.) but is not declared as an enum in the schema. Free-form string invites hallucinated values.