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

Annotations cover the safety profile (destructiveHint=true, openWorldHint=true, idempotentHint=false), and the description adds the two-phase render-then-queue behavior. But it omits important context: what happens if rendering succeeds and queueing fails, whether the scheduled post can be cancelled, which platforms are supported (left to schema), and auth requirements. For a destructive, open-world write tool this is thin but not misleading.

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?

A single sentence that front-loads the render step and then the queue step. No filler; every word 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?

This is a destructive, open-world composite tool with a nested body object, per-platform targeting, and timezone handling, yet the description is one sentence. It doesn't explain the relationship between output_type and body, the platform list values (schema only enumerates them in a description, not an enum), or what the tool returns despite having an output schema. Given the complexity and the destructive hint, more context is warranted.

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 100%, so parameters are already documented in the schema. The description names scheduled_at only as part of the flow, adding no syntax, format, or constraint detail beyond what the schema provides. Baseline 3 is correct when the schema does the heavy lifting.

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 two-step action: render a Studio card, then queue a ScheduledPost. The resource (Studio card / ScheduledPost) and the combination is clear. However, it doesn't distinguish itself from siblings like studio_card or schedule_post, which appear to be the constituent operations.

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?

No when-to-use guidance, no mention of alternatives such as calling studio_card and schedule_post separately, no preconditions. The agent has to infer that this is a convenience wrapper. Nothing tells it when this tool is preferred over the sibling primitives.

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