Draft archiving a Reddit entity

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

Annotations already mark destructiveHint=true and readOnlyHint=false, and the description adds meaningful context: Reddit has no hard delete, ARCHIVED is permanent, double confirmation is required, and this is only a draft/preview until confirm_and_apply is called. This goes well beyond the structured annotations.

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?

Every sentence carries essential information: action, irreversibility, Reddit constraint, preferred alternative, and execution workflow. It is compact, front-loaded, and free of filler.

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?

The description covers the destructive nature, the draft/execute split, the alternative tool, and the confirmation step. An output schema exists, so return details are not needed. The only gap is fuller parameter guidance, but the overall workflow is complete enough for correct invocation.

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%, so the description must compensate for parameter meaning. It only implies entity_type values by naming campaign, ad group, and ad. It does not explain entity_id or ad_account_id, their formats, or which entity_type values are accepted. Some meaning is inferable, but the burden is not fully met.

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 states a specific action ('Draft ARCHIVING') and the exact resources it applies to (Reddit campaign, ad group, or ad). The 'PREVIEW' marker and 'irreversible' qualifier make the tool's intent unmistakable and distinguish it from a plain remove or pause tool.

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?

Explicitly directs the agent to prefer pause_reddit_entity unless the user explicitly wants the entity gone. It also explains the double-confirmation requirement and names confirm_and_apply as the execution step, giving clear when-to-use and next-step guidance.

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