lower_auth_execution_priority

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

No annotations are provided, so the description carries full burden. It discloses the primary effect (lowering priority) but omits details about side effects, required permissions, reversibility, or impact on other executions. The description is too minimal 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?

The description is a single sentence, very concise and front-loaded. The parenthetical adds clarity without length. However, it could include a bit more information without becoming verbose.

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?

Despite simplicity, the description lacks specifics: what does 'lower' mean exactly (by one position? to the end?)? Are there prerequisites (execution must exist)? No output schema, but description doesn't compensate. Incomplete for a full understanding.

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%, with both parameters described ('Realm name', 'ID of the authentication execution'). The description adds no further meaning beyond the schema, so baseline 3 applies. No additional context like how to obtain the execution_id.

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 clearly states the action: 'Lower the priority of an authentication execution' with a parenthetical clarifying 'move it down in the flow'. It distinguishes from siblings like 'raise_auth_execution_priority' and 'lower_required_action_priority' by specifying the resource (authentication execution) and direction (lower).

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 does not explicitly state when to use this tool versus alternatives. It implies usage via the action verb, but lacks guidance on prerequisites or scenarios. No mention of when not to use or alternative tools like 'raise_auth_execution_priority'.

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