get_stream_details

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

Description states it returns all streams and clusters but does not disclose behavior beyond that—e.g., whether it's a read-only operation, any caching, or rate limits. No annotations present to fill the gap, so it's adequate but not thorough.

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 well-organized sentences: what it returns, when to use, and alternative tool. No unnecessary words.

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 zero-parameter tool with no output schema, the description fully covers its intended usage, distinguishing it from siblings and providing practical guidance.

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?

There are no parameters, so the description adds meaning by explaining what data is returned. Baseline 4 is appropriate as it adds value beyond the empty schema.

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?

Description clearly states it returns Kinesis data streams and Amazon MSK clusters with specific attributes (status, shard count, etc.). It distinguishes itself from sibling tool get_topic_details by specifying different scope.

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?

Explicitly tells when to use: when writing Kinesis producer/consumer code, checking stream capacity mode, or reviewing streaming architecture. Also explicitly identifies alternative sibling tool for topic-level details.

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