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

The "[write]" tag correctly corroborates readOnlyHint=false, but the annotations also declare destructiveHint=true and idempotentHint=false, and the description never explains what data is overwritten or whether re-running duplicates comments. It also omits how the openWorldHint platform interaction can fail (auth/token/rate limits).

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?

Two sentences, front-loaded with the action and its side effect, followed by the identifier mapping. Every clause carries information an agent needs to build a correct call.

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 write tool with no output schema, the description says only "return them" and does not describe the return shape, pagination, or how many comments a single sync pulls. Combined with the unexplained destructiveHint, an agent still lacks enough to predict the outcome of a call.

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?

With 0% schema description coverage, the description compensates well: it enumerates the platform enum (ig|fb|yt), maps post_id to the correct per-platform identifier (ig_post_id / fb_post_id / yt_video_id), and offers post_uuid as an alternative. It stops short of stating that only platform is required and that exactly one of post_id/post_uuid should be supplied.

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 uses a specific verb and resource ("Pull a post's comments from the platform into the panel") and clarifies the side effect with the "[write]" tag. However, it never names its closest sibling (list_post_comments), so an agent must infer how this differs from simply listing stored comments.

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 phrase "Pull ... into the panel" implies the tool ingests remote comments, but there is no explicit when-to-use statement, no exclusion of the sibling list_post_comments / list_comments_inbox tools, and no stated prerequisite (e.g., needing an already-connected account). Usage is only implied.

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