mcp_engram_lexicon_mint_word

Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?

With no annotations, the description takes on the full burden of disclosing behavior. It reveals upsert semantics, required fields (definition + etymology), internal operations (ProvLog, VSA OP_BIND, CRS ≥ 0.74), and the return value (action mint|update). Some ambiguity remains about the precise side effects of updates, but the description is notably transparent for a tool with no structured metadata.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Is the description appropriately sized, front-loaded, and free of redundancy?

The description is dense with domain-specific jargon and packs multiple ideas into a single unstructured paragraph. While every sentence earns its place, the lack of organization (no explicit sections) and heavy terminology make it less concise than ideal. A structured format would improve readability and clarity.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

For a tool without an output schema, the description covers the key contextual elements: return value, required inputs, internal processing, and an example. It does not address error cases or permissions, but given the complexity and the presence of a rich example, it is reasonably complete.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Although the schema provides 100% parameter coverage, the description adds valuable context through the few-shot example and clarifies that etymology is expected even though it is not marked as required. This goes beyond the schema's descriptions, enhancing parameter understanding.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Does the description clearly state what the tool does and how it differs from similar tools?

The description clearly identifies the tool as a lexicon seed/upsert operation with explicit mention of minting new words and updating existing ones. It specifies the resource (lexicon:word:*) and the intended action, distinguishing it from sibling tools focused on recall, visualization, or process management.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Does the description explain when to use this tool, when not to, or what alternatives exist?

The description provides clear context for when to use this tool (lexicon seeding) and references a 'Ritual' process, but it does not explicitly state when to avoid it or name alternative tools for similar tasks. Since the context is evident from the name and description, it earns a 4 rather than a 5.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.