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

Annotations only flag destructiveHint/openWorldHint/idempotent=false; the description adds the consequential behavior an agent must know: the user never sees the text before it goes live, timing is fixed at five minutes, and approval must be obtained first. This is exactly the context annotations cannot carry.

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?

Two dense sentences with no filler; the irreversible, high-stakes fact (user does not see the text first) is front-loaded right after the core action, and the alternative is saved for last.

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?

No output schema exists, but the description covers the action, the timing, the fan-out, the approval requirement, and the safer alternative — everything needed to invoke this destructive tool responsibly.

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%, so the baseline is 3. The description adds real semantic value beyond the schema by explaining the fan-out rule — one post per content hook per account — which explains why a small snapshot list can produce many posts and is not derivable from the array constraints 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?

States a specific verb (publish/schedule) and resource (posts from trend snapshots) with exact scope: 1–3 snapshots, one post per content hook per account, five minutes out. An agent can distinguish this from schedule_post and queue_trend_drafts without opening any schema.

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 names the prerequisite workflow (show get_trends' hooks and get explicit user approval) and the alternative with its selecting condition: 'Prefer queue_trend_drafts when they want to review.' Both when-to-use and when-to-use-something-else are covered.

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