wechat-title

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

With no annotations and no output schema, the description carries the disclosure burden. It does communicate that this is a lookup ('查询') scoped to '近N天' and '同赛道爆款文章', and that the result is '标题规律', but it leaves the concrete output shape, ordering, and pagination unspecified.

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?

A single sentence front-loads the platform and purpose ('公众号爆款标题参考') and then gives the query mechanism and scope. There is no filler and nothing that duplicates the schema.

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 simple two-parameter lookup, the description plus schema covers invocation essentials. However, without an output schema and with only the vague '标题规律' as the promised result, an agent cannot fully anticipate the response shape.

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%, so the baseline is 3; the schema already documents keyword as '赛道关键词' and days as '查询最近N天'. The description adds minor context about '同赛道爆款文章' but no new format, constraints, or semantics beyond the schema.

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 identifies a specific action ('按关键词查询') and resource ('公众号爆款标题参考' / '标题规律'), making clear it is a WeChat Official Account title-pattern lookup. It implicitly separates this from write/rewrite/search siblings, but does not explicitly name an alternative.

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?

Usage is implied: the tool should be used when the agent needs viral title patterns for WeChat articles in a niche within a recent window. However, there is no explicit when-to-use/when-not-to-use statement and no mention of alternatives such as wechat-write, wechat-rewrite, or xiaohongshu-title.

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