tomo_list_stream_servers

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

With no annotations provided, the description carries full burden for behavioral disclosure. It states the tool lists available experiences, implying no modification. However, it does not mention whether listing requires authentication, how many results can be expected, or if any default filtering applies. This is minimal but does not contradict anything.

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 sentence with no wasted words, front-loading the key verb and resource. It is appropriately concise for a zero-parameter 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?

Given the low complexity (zero parameters, no output schema, no nested objects), the description is nearly complete. It states what the tool lists and the scope. A minor gap is the lack of mention about return format or behavior when no experiences exist, but overall sufficient.

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 input schema has zero parameters and schema description coverage is 100%, so the description correctly implies no parameters are needed by stating a simple listing operation. No additional parameter details are required, and the description adds value by confirming the operation's nature.

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 clearly states the verb 'List' and the resource 'stream-server experiences' and specifies the scope 'on this control plane'. It distinguishes from siblings like tomo_list_rooms by naming a different resource type, though it could be more explicit about the contrast.

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 implies usage when you need to list stream-server experiences, but it provides no guidance on when not to use this tool or alternatives among siblings. For a simple listing tool with zero parameters, this is adequate, though explicit exclusions are missing.

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