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

Annotations (readOnly=false, destructive=false, openWorld=true, idempotent=false) cover the safety profile, and the description adds genuinely new behavioral context: append-to-end ordering, scheduling to next available slots, and the idempotency_key retry contract. It stops short of describing batch/partial-failure behavior for the items array or auth requirements, so not a 5.

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?

Three short sentences, front-loaded with purpose, then effect, then retry contract. No filler and every sentence adds information an agent can act on.

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 7-parameter mutation tool with nested items and no output schema, the definition covers purpose, side effect, and idempotency but omits multi-item failure handling, error/return shape, and the workspace/brand scoping that the siblings imply. Adequate but with notable gaps.

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 only 43% (below the 50% threshold), so the description should compensate. It does explain the idempotency_key semantics ('a repeat call with the same idempotency_key returns the original result'), which is valuable since that required parameter has no schema description, but leaves `id`, `brand_id`, `workspace_id`, `body`, and `query` essentially unexplained. Partial compensation only.

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?

Specific verb and resource: 'Add content items to the end of a distribution queue,' which is clearly distinct from the create-style siblings (create_queue, bulk_create_posts, create_scheduled_post). It does not, however, explicitly name or contrast those alternatives, so it stays at 4 rather than 5.

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 explains the consequential effect ('items publish in the queue's next available time slots') which implies the use case of scheduling existing content into a queue. But it gives no explicit when-not guidance, no prerequisites, and no pointer to the sibling (create_scheduled_post, bulk_create_posts) an agent might pick instead.

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