create_policy_gate

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

Discloses that redact mode is not supported, SDK blocks calls before execution, and at least one rule is required. No annotations provided, so description carries full burden and does so well.

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?

Messages are front-loaded and information-dense, but includes a longer example phrasing. Could be slightly trimmed without losing clarity, but overall efficient.

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 no output schema, description explains constraints, account limits, and SDK interaction. Does not mention return value, but likely expected for a creation tool. Adequately complete.

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%, baseline 3. Description adds value by summarizing parameter purposes (modelAllowlist, blockPii, blockSecrets), gives examples, and explains PII coverage details beyond 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?

Clearly states verb 'Create' and resource 'runtime policy gate', describes its function (model allowlist/PII/secret block), and distinguishes from sibling tools like delete/update/get policy gate. Includes example phrasing.

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?

Specifies Pro+ only, required rules (at least one), account limit (one), and SDK opt-in. Does not explicitly state when not to use, but constraints are clear.

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