think

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

Annotations already declare the mutation profile (readOnlyHint=false, destructiveHint=true, non-idempotent). The description usefully adds that a declared thought bypasses length/pattern gates to L4 and is rate-limited per user, which is real context beyond the annotations. However it never explains what a destructive write here actually affects or what happens to prior memory.

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 one-line purpose is front-loaded and the total length is short, which is good. But the second paragraph is dense with undefined internal jargon ("L4_DECLARABLE_KINDS", "spec S4") that consumes space without clarifying usage.

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 destructive, non-idempotent write tool with an output schema present, the description need not cover return values, but it should cover the five undocumented parameters and the layer-routing behavior. It does neither, leaving an agent unable to invoke the tool correctly beyond the single required `text` field.

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?

Schema description coverage is 0% across 6 parameters, so the description must carry the burden. It explains only `kind` (optional declaration hint, one of L4_DECLARABLE_KINDS) and leaves text, layer, user_id, wiki_type, and wiki_title wholly undocumented in both schema and prose.

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?

"Routing thoughts to correct memory layers based on importance and content" gives a rough verb+resource, but "Universal Primitive" is opaque jargon and the description never distinguishes this tool from siblings like memory_hook, dream, or project. An agent can guess it stores/places a thought but not how it differs from the other memory-writing tools.

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?

There is no when-to-use guidance, no prerequisites, and no named alternatives among the six siblings. The `kind` paragraph describes one parameter's effect but never tells the agent when to reach for think rather than evolve, memory_hook, or forget.

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