list_stream_spaces

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

The annotations already declare readOnlyHint=true and openWorldHint=true, and the description does not add behavioral details such as error cases, authentication requirements, or return behavior. It neither contradicts the annotations nor supplements them.

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 that front-loads the verb and object, with no unnecessary words or restatement of the name.

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?

Given the simple read-only list operation, the schema descriptions, output schema, and annotations, the one-line description is sufficient for an agent to invoke the tool. Some context about the concept of 'spaces' could enhance understanding, but sibling tools provide domain context.

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?

Both parameters are fully described in the schema (stream_key as 'Stream key to inspect' and instance_key as optional with default null). The description adds no new parameter semantics, so it meets the baseline for high schema coverage.

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 ('List') and names the resource ('spaces') with an explicit scope ('for a specific TimeBase stream'), making it distinct from sibling tools like list_streams and list_timebase_instances.

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 phrase 'for a specific TimeBase stream' implies the tool is for inspecting spaces associated with one stream, but it doesn't provide explicit when-to-use guidance or contrast with alternative tools such as list_streams, so the guidance is only implicit.

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