kuma_kuma_context

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

With no annotations, the description carries the full burden. It discloses that output is lean ('each call returns only what you need') and that init restores session state, but says nothing about read-only vs mutating behavior, permissions, or side effects across the nine actions.

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?

Front-loads the identity and the session-first directive before the action list, and the bracketed action glosses are compact. Slightly verbose in restating all nine actions, but each line earns its place as a routing hint.

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 nine-action multiplexed tool with no output schema, the description covers every action and key parameters adequately; the schema supplies the enum detail. It is nearly complete, missing only the behavioral/side-effect profile that annotations would otherwise carry.

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 100% and the action enum values are already documented in the schema, so the description largely restates them. It adds marginal value ('skeleton = compressed AST outline omitting bodies') but no new semantics for goal, scope, or target beyond the schema.

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 names a specific resource ('context & memory recall') and enumerates nine concrete actions, so an agent knows the tool's domain. It does not differentiate itself from the near-identically named sibling kuma_context, which leaves ambiguity about which context tool to pick.

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?

It gives an explicit timing cue ('Call FIRST each session') and embeds when-to-use hints per action, e.g. research 'before editing unfamiliar code', history for file rationale, and reuse 'before writing duplicate code'. It never names an alternative tool or states when NOT to use it.

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