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

With no annotations, the description carries the full burden and does so well: it discloses the org:admin permission requirement, the audit event (org.automation.set), propagation timing (immediate locally, ~30s to workers), and the important semantic that automation 'removes a review step, never a permission check.' The agent-seat and decider=console edge cases are behavior an agent could not derive from the schema.

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 purpose is front-loaded in a single sentence, followed by dense but relevant operational notes. The 'People only' passage is terse and slightly cryptic, but nearly every sentence earns its place for a governance-critical mutation; only minor tightening is possible.

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?

For a 3-parameter mutation tool with an output schema (so return format is covered elsewhere), the description supplies exactly the missing pieces: permissions, audit trail, propagation latency, and the safety semantics of what automation does and does not bypass. Nothing an agent needs to invoke it correctly is 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 the schema itself exhaustively documents level, overrides (with the full area list), and reset_overrides. The description adds no parameter-level meaning beyond that, so the baseline 3 applies.

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?

States a specific verb+resource: 'Set the org's automation level and per-area overrides.' An agent can immediately tell this is the write-side counterpart to org_automation_get. However, it never clarifies its boundary against other policy-setting siblings such as review_policy_set or memory_write_policy_set, so sibling differentiation is only implied by the naming pair.

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 the org-wide governance context and the org:admin requirement, but gives no explicit when-to-use guidance and no named alternatives. It does not tell the agent when to prefer this over review_policy_set, memory_write_policy_set, or the per-agent agent_routine_set, leaving the choice to inference.

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