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

Annotations already declare readOnly/idempotent/non-destructive, so safety is covered. The description adds useful behavior beyond that: it is read from TikTok 'just now' (live read, no caching implied) and explains that can_post_now false signals either TikTok refusing the account or video-length limits. But it is vague about the exact response shape and the trailing 'Free. Free.' is uninformative noise.

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 one long, run-on sentence with nested clauses ('...with what to show them and ask in your chat, read from TikTok just now: the account it goes to, who_can_see...') that is not front-loaded. The repeated 'Free. Free.' is redundant filler; structure and readability suffer significantly.

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?

With no output schema, the description carries some burden to describe return fields, and it does enumerate most of them. However, the wording is imprecise and the mapping of fields to actual response keys is unclear, leaving gaps for an agent assembling an owner-facing prompt.

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 coverage is 100% with a single required check_id already documented as coming from social_post's waiting_for_owner. The description adds no syntax or format detail beyond the schema, so the baseline 3 applies.

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 this reads a held TikTok post for its owner and enumerates fields (account, who_can_see, allow, disclosure labels, declaration, ask_owner), which conveys the verb and resource. However, the opening sentence is grammatically tangled ('A TikTok post social_post holds for its owner'), making the core action harder to extract than it should be. It does gesture at the sibling relationship with social_confirm_post, aiding differentiation.

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?

'Then social_confirm_post with their answer' implies this is the read step before confirming, and the schema says check_id comes from social_post's waiting_for_owner. But there is no explicit when-to-use/when-not guidance or statement of prerequisites in the description itself; usage must be inferred from the follow-up reference.

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