hicortex_search

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

With no annotations, the description must carry the behavioral burden. It discloses the scope (all agents, all sessions) which adds context, but it does not state whether the operation is read-only, how results are ordered, or what the return format is. A search operation implies safety, but the lack of explicit behavior disclosure leaves gaps.

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 dense sentences that front-load the purpose and then deliver a strong usage directive. Every word earns its place; no fluff or redundancy.

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 search tool with no output schema, the description should ideally explain what the agent will receive (e.g., list of memories, snippets, ordering). It also doesn't mention limitations or edge cases. It's adequate for when to use, but incomplete on mechanics.

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%, so the schema already documents all three parameters (query, limit, project) with descriptions. The tool description adds no extra parameter semantics, so the baseline of 3 applies.

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?

Clearly states the tool searches shared long-term memory across all agents and sessions, distinguishing it from siblings like hicortex_get or hicortex_recent. The verb 'search' and resource 'shared long-term memory' are specific and unambiguous.

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?

Explicitly instructs to call before assuming, guessing, or asking the user about prior information, and even gives a trigger condition ('If you are about to write...'). However, it does not mention when not to use it or alternatives like hicortex_recent for recent items, so it stops short of full 5.

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