apex_dry_run_preview

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

Annotations already provide idempotentHint=true and destructiveHint=false. The description adds essential behavioral context by clarifying that it logs PL/SQL without executing and returns the log when disabled. This goes beyond the annotations and clarifies the state-changing nature (readOnlyHint=false) without contradiction.

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 concise sentences, front-loaded with the primary action and effect. Every word carries meaning, with no filler or repetition of schema details.

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 one-parameter toggle with an output schema present, the description adequately covers the core behavior, the condition for returning the log, and the mode's purpose. No additional details are necessary.

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 schema fully describes the single boolean parameter with a default value and clear explanation of true/false semantics. The description adds no significant meaning beyond restating the toggle behavior, so the score aligns with the high schema coverage baseline.

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: 'Toggle dry-run mode' with the specific resource (PL/SQL execution). It explains the effect (log without executing) and the return behavior (log when disabled), distinguishing it from siblings like apex_run_sql which actually execute code.

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 for previewing or testing PL/SQL without side effects, but it does not explicitly state when to use it over alternatives or provide context like 'use before executing SQL'. However, the functionality is self-explanatory enough for an agent to infer typical usage.

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