ae_set_workflow_preferences

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

No annotations exist, so the description must carry the full burden of behavioral disclosure. It confirms a write operation but does not say whether settings persist, whether they merge with existing preferences, what they affect, or whether any preconditions exist. This is a significant gap for a mutation tool.

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?

One tight sentence, front-loaded with the verb and resource, and free of filler. It is concise, though the brevity comes at the cost of detail needed for a 9-parameter tool.

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 9 optional parameters, no annotations, and no output schema, a single generic sentence is incomplete. It does not cover defaults, merge/persistence behavior, valid value context, or what happens after setting preferences.

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 0%, and the description only groups parameters into two broad buckets without mapping to the 9 fields or clarifying value semantics. It fails to compensate for the undocumented schema, leaving agents to infer meaning from enums and names alone.

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 names a specific verb ('Set') and a distinct resource ('workflow preferences'), and scopes it to autonomous/approval workflow behavior plus project brand defaults. It does not explicitly compare with ae_get_workflow_preferences, but the resource is identifiable enough to separate it from sibling editing tools.

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 is given on when to use this tool versus ae_get_workflow_preferences or other workflow-related tools. The phrase 'high-level editing workflows' implies a context but provides no decision rule or exclusions.

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