wechat_validate_article_bundle

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

Annotations already provide readOnlyHint=true and destructiveHint=false, and the description adds valuable behavior beyond them: local execution, no upload, and image preprocessing. It also clarifies that bundle_path refers to an article folder inside the official-account working directory rather than an arbitrary path.

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 short, purposeful sentences: the first identifies the operation and exclusions, the second defines the sole parameter. There is no filler, repetition of schema, or unnecessary detail.

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 definition covers local/no-upload behavior and the parameter, which is adequate for a one-parameter tool, but it does not describe what the tool returns on success/failure or what 'preprocess' entails. Since there is no output schema, an agent is left without knowledge of the validation result format.

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 0%, so the description must carry the parameter meaning. It explains bundle_path as '公众号工作目录内的文章文件夹路径' (article folder path within the official-account working directory), which is far more useful than the bare string type. It does not specify relative vs. absolute formatting, but is sufficient for invocation.

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 a specific verb, 'validate', and a concrete operation, 'preprocess images', with a clear scope: local only, '不上传' (no upload). This distinguishes it from siblings like wechat_create_draft_from_bundle without requiring schema inspection.

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 '本地校验...不上传' gives useful context that this is a local pre-upload step, but it never names alternatives or explicitly says when to use this tool versus checking access or creating a draft. The usage conditions are implied rather than stated.

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