create_rich_text_post

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

With no annotations, the description carries full burden for behavioral traits. It states the tool creates a post, but does not disclose side effects (e.g., whether it replaces an existing post), error conditions, rate limits, or required auth. The description adds little beyond the basic purpose.

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, front-loaded sentence that efficiently states the core function. However, for a tool with nested parameters, it could be expanded to include key parameter details without losing conciseness.

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 (3 parameters, nested objects, no output schema, no annotations), the description is severely incomplete. It omits how to structure facets and embed, any constraints (e.g., byteStart/byteEnd), and what the response contains. Essential for correct invocation is missing.

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 0%, so the description must compensate. It maps high-level features (mentions, links, etc.) to parameters, but fails to explain the complex nested structure of 'facets' (byte indices, feature types) and 'embed' (sub-objects per type). The agent would struggle to construct valid inputs without deeper knowledge.

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 tool creates a post with rich text formatting, explicitly listing mentions, links, hashtags, and media embeds. It distinguishes from sibling tools like 'create_post' (likely simpler) and 'create_thread' (multiple posts), making the purpose specific and actionable.

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. It does not mention that 'create_post' might be preferred for plain text, nor does it specify prerequisites or excluded scenarios. The agent must infer usage from the name alone.

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