ae_get_workflow_preferences

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

With no annotations, the description carries the behavioral burden and does so reasonably: it explicitly states this is a read operation and explains the semantic difference between approval and autonomous modes. It does not mention edge cases like unset preferences or which defaults are returned, but for a zero-parameter getter the disclosed behavior is adequate.

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 description is two sentences with no filler: the first sentence states exactly what is read, and the second provides meaningful context about mode semantics. It is front-loaded and every sentence earns its place.

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 simple zero-parameter getter with no output schema, the description covers the tool's purpose and the meaning of the two modes it returns. It is slightly incomplete in that it does not describe the shape of the returned preferences or behavior when nothing has been configured, but those gaps are minor for this complexity level.

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?

The tool has zero parameters, so there is nothing for the description to explain beyond schema coverage. The baseline of 4 applies because no parameter documentation burden exists.

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 uses a specific verb ('Read') and identifies the exact resources read: workflow mode, edit mode, and brand defaults. It clearly communicates the tool's scope but does not explicitly differentiate from the sibling set_workflow_preferences, relying on the verb instead.

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 usage by explaining what the workflow modes mean and noting that approval mode is the safe default, so an agent can infer when checking current preferences is relevant. However, it never explicitly states when to call this tool versus alternatives, nor does it name any when-not-to-use conditions.

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