Create a post

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

With no annotations available, the description carries the full behavioral burden and does so admirably. It discloses verification by read-back, refusal to double-post, and honest reporting of verification failure, which are meaningful behavioral traits beyond a simple 'create' operation.

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 with no filler. Every clause adds useful behavioral information about publishing, verification, and duplicate prevention.

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 a one-parameter publish tool, the description covers the main action, verification, idempotency, and error honesty. It does not provide a full return schema or auth requirements, but the description still gives enough for an agent to call the tool correctly.

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 implicitly defines the lone `text` parameter as the post content, but does not add details like maximum length, formatting, or special handling. The coverage is adequate for one parameter but not thorough.

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 states a specific action ('Publishes a text post') and resource, and also differentiates from siblings by mentioning read-back verification and double-post prevention. An agent can clearly distinguish create_post from edit_post, delete_post, and comment.

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 clearly implies when to use the tool: when publishing a new text post. It does not explicitly discuss exclusions or compare with sibling tools, but the purpose statement is unambiguous enough for this simple operation.

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