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

No annotations are provided, so the description carries the full behavioral burden, and it delivers almost nothing: it does not state that this is a read-only lookup, what the response contains, whether authentication is required (the schema hints at a _token fallback), or any rate-limit/error behavior. Only the implied 'detail retrieval' framing gives any signal.

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?

It is a single front-loaded phrase with zero redundancy, so nothing needs trimming, but the terseness is under-specification rather than genuine conciseness — it conveys far less than an agent needs for an ambiguous platform-scoped tool.

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 annotations, no output schema, and a description that is only a title-like phrase, the definition is thin for a tool that must be distinguished from ~29 platform siblings. An agent can guess the intent from the name but has no support for calling it confidently or interpreting results.

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%: `code` is documented as the post shortcode and `_token` as an alternative auth token with a preferred header alternative. The description adds no parameter meaning at all, so the baseline 3 for fully documented schemas 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 'Instagram帖子详情' names the resource (an Instagram post) and implies retrieval of its details, which distinguishes it from sibling tools clearly scoped to other platforms (xhs_note, weibo_post, tiktok_video). However, it is a bare noun phrase with no verb and no scope qualifiers (which fields, single vs. bulk), so the purpose is only implied rather than stated.

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?

There is no guidance on when to use this tool versus alternatives such as xhs_note, weibo_post, or tw_post, nor any prerequisite (e.g., that a valid shortcode is required) or exclusion. The agent must infer platform routing purely from the tool name.

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