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

Beyond annotations, the description discloses that the separate social:publish permission is required and that X charges the publisher's X account. It also explains timing behavior for approval-waiting posts versus drafts and that publishing occurs on behalf of the brand, adding important operational context for a destructive, open-world mutation.

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 front-loaded with the action and resource, then supplies timing, permission, and cost details without repetition. Every sentence carries actionable information for invocation.

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?

It covers the key behavioral context for a publishing mutation: state-dependent timing, required permission, external cost, and the source of post_id. The main gap is that title_id remains unexplained, which may leave ambiguity about that required parameter.

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 100%, so the baseline is 3. The description adds useful meaning for post_id by saying it comes from list_social_posts, but it does not explain title_id beyond the schema's terse 'TitleID.' description.

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 verb and resource: publishing a social post on X on behalf of the brand. It clearly distinguishes approval-waiting posts from drafts and references list_social_posts as the source of post_id, so an agent can identify the operation without opening the schema.

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 gives clear contextual guidance: pending-approval posts publish at their proposed time or immediately if that time has passed, while drafts publish now. It does not explicitly name alternative tools such as draft_social_post or publish_social_reply, but the states and required permission make the usage context clear.

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