create_post

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

No annotations provided, so description should carry full burden. It only states the action without disclosing behavioral traits such as authentication requirements, rate limits, or success/failure outcomes.

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?

Extremely concise single sentence, front-loaded with key information. Every word contributes to understanding the tool's purpose.

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 5 parameters (1 required), no output schema, and no annotations, the description is insufficient. It does not explain return value, error cases, or contextual relationships with siblings like delete_post or get_post.

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 100%, so description adds minimal extra meaning. It mentions optional media, reply, or quote which maps to parameters, but no further constraints or behavioral details beyond schema.

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?

Description clearly states verb 'Post', resource 'new post', and optional features like media, reply, or quote. Distinct from siblings such as create_thread and repost_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?

Implied usage for creating a single post, but no explicit guidance on when to use versus alternatives like create_thread. No exclusions or when-not scenarios mentioned.

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