create_post

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 mentions 'Create' (implying a write operation) but does not disclose any side effects, authentication requirements, rate limits, or what happens upon success/failure. This is a significant gap for a mutation tool.

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, short sentence that is front-loaded with the essential action and resource. It is concise and easy to parse, though it omits other useful details. It earns high marks for efficiency but is slightly under-specified for a complete tool description.

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?

This is a simple tool with one parameter and no output schema, but the description is minimal. It does not explain what the tool returns (e.g., the created post object), whether it requires special permissions, or any other behavioral context. Given no annotations, the description leaves important gaps for an agent to invoke the tool confidently.

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 fully documents the single parameter 'text' with type, maxLength, and a clear description. The tool description does not mention parameters, so it adds no additional meaning. Given the schema coverage is 100%, a baseline score of 3 is appropriate.

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's function with a specific verb ('Create') and resource ('a new post on Twitter/X'), and it distinguishes itself from sibling tools which are all read/search operations (read_posts, get_post, search_posts). This is unambiguous and action-oriented.

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 usage is implied by the verb 'Create' in contrast to the read-oriented sibling tools, but there is no explicit guidance on when to use this tool versus alternatives, nor any exclusions or prerequisites. It's clear that this is for creating posts, but no further context is given.

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