add_post_to_queue

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

No annotations are provided, so the description carries full burden. It only states what the tool does, not behavioral traits like idempotency, error handling, side effects (e.g., whether it immediately adds to queue or creates a draft), or prerequisites. For a complex tool with 12 parameters, this is insufficient.

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 a single sentence, which is concise. It front-loads the core action. However, for a tool with many parameters, a slightly more structured description (e.g., listing key parameters or behaviors) could be beneficial.

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?

Given the complexity (12 parameters, nested objects, no output schema), the description is too minimal. It does not explain what the tool returns, whether it validates inputs, or any limitations (e.g., queue capacity). The high parameter count demands more context.

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 the baseline is 3. The description adds no additional meaning beyond the schema; it merely summarizes the action. The schema already provides descriptions for each parameter, so the tool definition does not need to repeat them.

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 ('Create a Postoria post and add it to a publishing queue'). The verb 'create' and 'add' are specific, and the resource (post, queue) is named. This distinguishes it from siblings like publish_post_now and schedule_post.

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 guidance on when to use this tool versus alternatives. Sibling tools include publish_post_now and schedule_post, but the description does not specify when to choose this one over them. The context signals mention 12 parameters and 3 required, but no usage hints.

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