xhs_publish

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

The description discloses the requirement to be logged into the creator platform, which is a key behavioral constraint. There are no annotations to contradict, and the description adds context about the operation without being misleading.

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 extremely concise with three key sentences plus the Args section. No redundant information; every part contributes to understanding the 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?

The description covers input parameters and a critical prerequisite. Although it does not detail return values, an output schema exists, so that is not required. It is sufficient for a standard publish tool.

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?

Parameter descriptions add significant value beyond the schema: title must be ≤20 characters, content ≤1000 characters, and images must be local paths. This compensates for the 0% schema description coverage.

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 clearly states the verb '发布' (publish) and the specific resource '小红书图文笔记' (Xiaohongshu image-text note). It distinguishes from sibling tools like xhs_comment or xhs_search, which have different purposes.

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?

It mentions the prerequisite of login to the creator platform, which gives context. However, it does not provide explicit guidance on when to use this tool versus alternatives, nor does it exclude any conditions.

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