get_stream_time_range

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

The annotations already declare readOnlyHint=true and openWorldHint=true, indicating a safe read operation. The description adds the behavioral detail that the time range is in UTC, which is useful. However, it does not disclose behavior for missing streams or provide details about output format beyond what the output schema already covers.

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 words. It front-loads the core action and result, making it easy to scan and understand.

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 read-only tool with a well-described schema and an output schema present, the description is adequately complete. It covers the key behavioral nuance (UTC timezone) and the tool's scope (specific stream). The only minor gap is the lack of explicit differentiation from similar sibling tools, but this is not critical given the overall simplicity.

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%, with clear descriptions for stream_key ('Stream key to inspect') and instance_key ('TB instance key. Required when multiple TimeBase instances are configured.'). The description adds no extra parameter meaning beyond what the schema already provides, so a baseline score of 3 is appropriate.

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 'Get the time range of a specific stream in UTC' clearly identifies the verb (get), resource (stream), and result (time range in UTC). It distinguishes itself from the sibling 'get_stream_space_time_range' by specifying 'specific stream' rather than 'stream space', though it does not explicitly name the alternative.

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?

The description provides no guidance on when to use this tool versus alternatives like get_stream_space_time_range, nor does it mention prerequisites or exclusions. The only context is the short descriptive sentence, leaving the agent to infer usage from the tool name.

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