Create CORS Policy

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

Disclosure that all seven fields are required and policyId optional adds value beyond annotations. Returns policy ID. Does not contradict annotations; provides useful behavioral context.

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?

Three concise sentences, front-loaded with purpose, no redundancy.

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?

Covers creation process, required fields, optional policyId, and return value. Could mention global scope more explicitly, but adequate for an agent.

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 coverage is 100% but description summarizes required fields, optional policyId, and return value, adding context beyond schema descriptions.

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?

Clear verb 'Create' and specific resource 'CORS policy on the global AM CorsService' distinguish it from sibling create tools like createJourney or createManagedObject.

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?

Describes creation context but lacks explicit guidance on when to use this tool vs alternatives like updateCorsPolicy or deleteCorsPolicy. No conditions or exclusions mentioned.

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