kinesis_describe_stream

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

With no annotations, the description carries the full burden. It discloses that the tool operates 'in LocalStack', which is useful environment context, but it does not describe what happens if the stream doesn't exist, what information is returned, or any side effects. Since this is a describe operation, safety is implied, but no explicit behavioral traits are disclosed.

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, focused sentence that is easy to parse and front-loads the action. It is appropriately concise for a simple read operation, though it could arguably be expanded with more detail without becoming wasteful.

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 one-parameter description tool with no output schema and no annotations, the description provides the minimum viable context: it identifies the resource and environment. However, it does not indicate what a typical response contains (e.g., stream status, shard count) or any edge-cases, leaving gaps in completeness.

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 100% coverage with the parameter 'name' described as 'Stream name'. The description does not add further semantic meaning beyond the schema's own documentation, so the baseline of 3 applies.

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 the specific verb 'Describe' with a clear resource 'a Kinesis stream', and adds the 'LocalStack' context. It distinguishes from sibling tools like kinesis_list_streams (list) and kinesis_get_records (get data) by clearly indicating a description operation.

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?

No guidance is provided on when to use this tool versus alternatives. There is no mention of prerequisites, e.g., needing to list streams first, or situations where get_records would be more appropriate. The usage context is only implied by the verb, so the agent receives no direct behavioral instruction.

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