engain_create_post_task

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

Without annotations, the description must fully disclose behavioral traits. It only mentions credit cost. It does not state whether the action is destructive, whether authentication is required, whether it creates public content, or any side effects. This is insufficient for informed invocation.

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 very short (two sentences) and front-loads the primary purpose. It is efficient but could incorporate more useful details without becoming verbose.

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 tool's complexity (7 parameters, nested objects, no output schema), the description is insufficient. It omits required parameters, return values, and parameter details. The credit cost note is helpful but cannot compensate for the lack of complete guidance.

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 only 14% (only 'projectId' has a description). The tool description does not explain any parameters beyond the tool's purpose. For example, 'rank' and its nested fields are not described, nor is 'labels' or 'scheduledAt'. The description adds minimal value beyond what the schema already provides.

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 Reddit post task') and the target resource ('in a subreddit'). It effectively distinguishes this tool from sibling tools like engain_create_comment_task and engain_create_reply_task, as those involve different actions.

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 is provided on when to use this tool versus alternatives. The mention of 'Spends CREDITS (typically 10)' gives cost insight but not situational context. Absence of prerequisites, specific use cases, or exclusions leaves the agent without decision-making support.

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