kernel_chat_patterns

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

No annotations are provided, so the description carries the full behavioral burden. It implies a read ("View") but never states whether results are computed on demand or cached, over what time window or conversation scope, whether they are per-user or global, or what the payload looks like. For a zero-parameter tool that implicitly aggregates across all data, these omissions matter.

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?

A single compact sentence with the resource front-loaded and no filler. It is efficient but borders on under-specification rather than tightness — brevity is achieved by omitting scope and output details.

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?

With zero parameters, no annotations, and no output schema, the description is the only source of information about this tool, and it supplies one vague sentence. Scope, freshness, and result shape are all undefined, which is inadequate for a tool whose entire contract lives in prose.

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 tool takes no parameters and the schema is an empty object, so there is nothing for the description to disambiguate. Baseline of 4 applies; the description could have noted the absence of filtering, but no parameter meaning is required.

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?

"View detected temporal and behavioral patterns from chat conversations" gives a verb (view), a resource (patterns), and qualifies them as temporal/behavioral. However, it largely restates the name kernel_chat_patterns and never specifies what a "pattern" is — clusters, recurring topics, activity cadence, sentiment trends. An agent cannot confidently distinguish it from siblings like kernel_chat_analyze or kernel_chat_concepts on this text alone.

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 exclusion, and no reference to any sibling tool. With kernel_chat_analyze, kernel_chat_concepts, and kernel_chat_search in the same family, the agent is left to guess which produces derived insight versus raw retrieval.

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