x_api_create_posts

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

With no annotations, the description fully shoulders the burden by disclosing mutating/high-risk status, required OAuth permissions, common failure conditions, and a safety warning. It even explains environment-selection behavior for auth resolution. This is exemplary transparency.

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 longer than typical but uses clear label-framed sections, making information scannable. Every section adds necessary context—permissions, risk, response shape, failure modes—with no filler.

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 7-parameter schema with no descriptions and no output schema, the description provides expected response shape, failure conditions, prerequisites, and an example. It covers the critical operational aspects needed to invoke the tool safely and 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 descriptions are absent (0% coverage), so the description compensates by explaining scopeTenantId, scopeUserId/scopeAccountId selection, credentialKey behavior, and body usage. However, authorizationKey and preferredAuthType are not explicitly explained, so it is not fully complete but is strong.

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 opens with 'Create or Edit Post,' clearly identifying the tool's function and resource. It is distinct enough from siblings like x_api_delete_posts, though it does not explicitly differentiate from other post-related create/edit operations. The verb-resource pairing is specific and unambiguous.

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 explicit 'Use when' and 'Do not use when' conditions, including directing users away when only exploring and toward x_schema_discovery or x_query_suggestion. It also lists recommended prerequisite and follow-up tools, giving clear context for when to use this tool versus alternatives.

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