kinesis_put_records

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

With no annotations provided, the description carries the burden of behavioral disclosure. It adds useful context: 'in LocalStack' and 'max 500'. However, it doesn't mention failure behavior, error handling, or whether the operation is idempotent, leaving significant gaps for a mutation tool.

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 that is concise and front-loaded with the core action. Every word contributes value ('multiple', 'LocalStack', 'max 500'), with no unnecessary fluff or repetition.

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?

The description is adequate for a simple batch put operation: it identifies the stream, the action, and a key limit. However, the lack of an output schema means the agent gets no information about return values or partial failures, and no mention of stream existence requirements, leaving some contextual gaps.

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% with simple descriptions for streamName and records. The tool description adds no additional parameter meaning beyond what the schema already provides, so the baseline score 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 clearly states the tool's function: 'Put multiple records onto a Kinesis stream' — a specific verb plus resource. It differentiates from the sibling tool 'kinesis_put_record' by emphasizing 'multiple' and the 'max 500' limit, making its batch purpose unambiguous.

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 multiple records need to be written, and the 'max 500' limit conveys an important constraint. However, it doesn't explicitly say when not to use it (e.g., 'for a single record use kinesis_put_record') or mention prerequisites like the stream needing to exist.

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