technocore_search

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

No annotations are provided, so the description carries the full burden of behavioral disclosure. It only says 'search' without revealing return format, result ordering, default room behavior, or whether the operation is read-only. This is not misleading, but it is minimal.

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 five-word sentence states the core operation with no redundancy. It is front-loaded and appropriately compact for a simple search tool.

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?

The tool is simple and the input schema is fully self-documenting, so some missing prose detail is acceptable. However, with no output schema or annotations, the description does not tell the agent what a result looks like or how the default 'all rooms' search behaves, leaving a moderate gap.

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 schema covers 100% of parameters with descriptions for query, limit, and rooms, so the baseline is 3. The phrase 'across rooms' loosely corresponds to the rooms parameter, but the description adds no substantive meaning beyond what the schema already provides.

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 states a specific verb ('Search'), a resource ('messages'), and a scope ('across rooms'), clearly conveying what the tool does. However, it does not explicitly differentiate itself from siblings like technocore_read or technocore_stream, which may also deal with messages.

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?

No guidance is given about when to use this tool instead of alternatives. There are no exclusions, prerequisites, or mention of what scenarios favor search over read or stream, leaving the agent to infer usage from the tool name alone.

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