victorialogs.search_stream

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

Annotations already declare readOnlyHint, idempotentHint, openWorldHint and destructiveHint, so the safety profile is covered. The description adds the default time window, but that value is already the rangeSec schema default (3600), and it says nothing about pagination or the 500 limit cap. Adds marginal context beyond annotations.

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?

Three short sentences, front-loaded with the core operation and followed by the discovery hint and default window. No filler; every sentence carries actionable information.

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 6-parameter, no-output-schema tool this is thin: four of six parameters are unexplained and there is no note on what a result contains or how limit interacts with the time window. The required parameter and its discovery path are covered, which keeps it at minimum-viable rather than inadequate.

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 0% across 6 parameters, so the description carries the full burden and largely fails. It restates the streamId pattern (already encoded in the schema) but never explains filter syntax, limit behavior, or the start/end vs rangeSec relationship.

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?

States a specific verb and resource ('Search a VictoriaLogs stream') plus the key identifying field (48-character hex _stream_id), which is enough to separate it from the other search siblings. It stops short of explicitly contrasting with search_logs/search_uuid, so an agent still has to infer which search family applies.

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?

Gives real routing guidance: it names list_streams as the way to discover IDs and states the default time window. It lacks an explicit 'when not to use' (e.g. use search_logs when you don't have a stream ID), but the discovery pointer handles the main selection decision.

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