mcp_engram_promote_hot_batch

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

No annotations are provided, so the description must carry the full burden. It discloses that each concept is promoted individually but in one call, but lacks details on permissions, side effects, or failure modes.

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?

Two sentences, front-loaded with purpose, no fluff. Every sentence serves a clear role.

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 batch variant with one parameter and no output schema, the description adequately covers the use case and efficiency benefit. Could mention return value or error behavior, but not essential.

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?

The description repeats the schema's description for the only parameter 'concepts', adding no additional meaning. With 100% schema coverage, the baseline is 3, and no extra value is provided.

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 states it batch promotes multiple concepts to the hot path, specifying the target (LegView, backend hot cache, hot_set). It effectively distinguishes from sibling mcp_engram_promote_hot by noting it reduces round-trips vs repeated single calls.

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?

Provides explicit usage context: 'Used in optimized wake-up after rehydrate to batch hot anchors/tiles/traces.' This guides when to use. Lacks explicit when-not-to-use guidance, but the context implies it's for batch operations.

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