technocore_stream

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

With no annotations provided, the description carries the full behavioral disclosure burden. It meaningfully discloses that the operation is a one-time snapshot, which is a useful behavioral distinction from 'stream' semantics. However, it does not state whether messages are consumed/destroyed, how ordering works, or whether any side effects occur.

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 description is a single concise sentence with no filler or redundancy. The core purpose is front-loaded, and the clarifying 'one-time snapshot' qualifier earns its place.

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 simple snapshot tool with two well-described parameters, the description is mostly adequate. However, with no output schema and no usage guidance, an agent is left without information on the return format, ordering of messages, or how this differs from technocore_say/technocore_search. A bit more behavioral context would round it out.

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 both parameters already have meaningful descriptions ('Room name to stream from' and 'Number of recent messages to get'). The tool description adds no additional parameter-level semantics, so the baseline score 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?

The description uses a specific verb and resource: 'Get the latest messages from a room,' and the parenthetical 'one-time snapshot' clarifies that this is not a live/continuous stream. This distinguishes it from sibling tools like technocore_say (sending) and technocore_search (querying), so an agent can tell them apart without opening schemas.

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 explicit guidance is given about when to use this tool versus alternatives such as technocore_say or technocore_search. The 'one-time snapshot' phrase implies it is for a single fetch rather than ongoing streaming, but the agent must infer this rather than being told directly.

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