process_lambda_pipeline

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

With no annotations, the description must disclose all behavioral traits. It clearly states the migration action and transformations, but does not note whether the source Hot Tier data is deleted, whether the operation is idempotent, or any required permissions. This leaves significant behavioral ambiguity.

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 concise sentence that packs the main action and three sub-operations. It is front-loaded and free of redundant 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?

The description gives a solid overview but omits important operational details such as idempotency, source data retention, and parameter semantics. With no annotations and a simple schema, the description should provide more completeness for a migration tool.

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 a single parameter (max_batch_size) with no description, and the tool description does not explain its meaning or effect. The parameter name is somewhat self-explanatory, but without explicit guidance, the agent cannot infer how batch size impacts the migration.

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 primary function: migrating Hot Tier events to Cold Storage. It also lists specific operations (ID stitching, PII anonymization, priority scoring), which distinguishes it from sibling ingestion/export tools.

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 provides no guidance on when to use this tool versus alternatives like ingest_batch_api_poll or export_to_data_warehouse. It lacks any context or prerequisites for invoking the migration.

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