get_ksqldb_streams

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

Annotations already declare readOnlyHint=true, idempotentHint=true, and destructiveHint=false, so the description is not burdened with safety disclosure. It adds only the 'all' scope, indicating no filtering, but does not describe pagination, output shape, or any other runtime behavior.

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 precise sentence with no filler or redundant information. It is appropriately front-loaded and immediately conveys the tool's action and target resource.

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 list operation with full schema coverage and robust annotations, the description is nearly complete for selecting and invoking the tool. It could be more complete by indicating what a stream listing returns or any cluster-scoping nuance, but nothing essential to invocation is missing.

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%, and both required parameters already have clear descriptions ('ksqlDB cluster name' and 'Cluster name'). The tool description adds no additional parameter context, so the baseline 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 states a specific verb ('List') and resource ('all ksqlDB streams'), clearly distinguishing this from sibling tools like get_ksqldb_tables, get_ksqldb_queries, and get_ksqldb_info. The resource named in the description is enough for an agent to select the right tool 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?

The description implies use when the caller needs the complete set of ksqlDB streams, but it provides no explicit when-to-use guidance, no exclusions, and no mention of alternatives such as get_ksqldb_tables or get_ksqldb_queries. The sibling names exist, but the description itself does not route the agent.

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