s3_setup_cors

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

No annotations are provided, so the description carries full responsibility for behavior. It reveals this is a mutation ('Configure') but does not disclose whether existing CORS rules are merged or overwritten, whether API key authentication is mandatory, or what happens on failure. For a mutating setup tool, this is a notable gap.

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?

A single well-structured sentence conveys action, resource, and purpose without bloat. The parenthetical '(Pro)' is minor noise but does not impair comprehension or selection.

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 schema covers invocation completely with bucket_name, allowed_origins, and allowed_methods required, and the description explains why this tool matters. Missing context is mainly behavioral: what the API call changes, whether existing CORS settings are affected, and expected output/confirmation are absent.

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% and each parameter already has a clear description, so the schema carries the semantic weight. The tool description adds only the cross-origin browser context and does not explain parameter relationships (e.g., allowed_methods vs max_age) beyond 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?

Description uses a specific verb ('Configure'), resource ('S3 CORS rules'), and rationale ('cross-origin browser access'). This is far more informative than a tautology and distinguishable from broader S3 or CORS sibling tools, though it does not explicitly name an alternative to rule out.

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 on when to choose this tool over related siblings such as cors_generate_policy, cors_analyze_config, or s3_generate_policy. No mention of prerequisites like an existing bucket, IAM permissions, or whether this replaces existing CORS rules.

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