eventbridge_put_targets

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

With no annotations provided, the description carries the full burden for behavioral disclosure. It only says 'Add or update' without explaining mutation behavior, potential overwriting semantics, permission requirements, or error conditions. This is insufficient 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 key verb and resource. Every word adds value and there is no redundant information.

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 minimal for a tool with no output schema and no annotations. It lacks context about prerequisites (rule must exist), behavior on duplicate targets, or any LocalStack-specific considerations. The schema covers parameters but not usage context, leaving the description incomplete for effective invocation.

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%, so the schema already defines each parameter clearly. The description does not add additional meaning beyond mentioning 'targets' and 'EventBridge rule', providing only a baseline benefit over the 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?

The description clearly states the verb 'Add or update' and the resource 'targets for an EventBridge rule', which distinguishes it from sibling tools like eventbridge_remove_targets, eventbridge_list_targets, and eventbridge_put_rule. The scope 'in LocalStack' provides context.

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 for adding/updating targets on an existing rule but does not explicitly state when to use this over alternatives or any prerequisites. There is no mention of needing to create the rule first or that eventbridge_put_rule should be used for rule creation.

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