set_aws_response_policy

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

The description implies a mutation ('set') but offers no details on idempotency, reversibility, or required permissions. No annotations are provided, so the description carries the full burden but fails to disclose behavioral traits.

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 short sentence, which is concise but lacks structure. It is front-loaded but under-specified, missing important details. It could include more information without being verbose.

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?

Given the tool's role among many sibling configuration tools and the absence of an output schema, the description is incomplete. It does not explain return values, usage context, or how it relates to other tools, leaving the agent without sufficient information.

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% description coverage for both parameters ('domain' and 'policy_id'), so the schema already explains their meaning. The description adds no additional semantic value beyond what the schema provides.

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 states the verb 'set' and the resource 'AWS response header policy', which is clear. However, it does not distinguish this tool from sibling tools like set_aws_origin_request_policy, both of which set policies. The schema shows it sets a response policy by ID, but the description lacks this differentiation.

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. Given numerous sibling set_* tools, the agent has no context for selection. No exclusions or when-not-to-use are mentioned.

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