create_post_with_restrictions

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

With no annotations provided, the description carries the full burden of behavioral disclosure. It merely states the action and mentions 'restrictions' but does not reveal any side effects, permission requirements, or limitations. The nature of the restrictions and their enforcement is left undefined.

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, compact sentence with no redundant wording or fluff. It is efficiently front-loaded, though it could benefit from a brief preview of the restriction options to improve structure.

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 an 8-parameter mutation tool with no annotations and no output schema, the description is under-specified. It does not explain what 'advanced' restrictions mean, potential dependencies between parameters, or expected outcomes. The schema covers parameter syntax but the overall tool context remains incomplete for an agent to confidently invoke it.

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?

The input schema provides thorough descriptions for all 8 parameters, including enums for reply_control and audience_control. The description adds no additional parameter-level meaning, so the baseline of 3 applies given the high schema coverage.

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 uses the specific verb 'Create' and identifies the resource 'post,' with the qualifier 'advanced reply and audience restrictions' distinguishing it from sibling tools like create_thread_chain or create_reply. However, 'advanced' is vague and no explicit sibling names are mentioned, so it stops short of a 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 provides no guidance on when to use this tool versus alternatives such as create_thread_chain or publish_thread. It only states the action without any context about when posting with restrictions is appropriate or how it differs from other posting tools.

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