Open WeChat Article

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

Annotations already indicate the tool is not read-only, idempotent, or destructive, providing a baseline. The description adds that it returns 'structured page status' and emphasizes the lack of full extraction, but it does not disclose side effects like browser launch, tab management, or manual verification waits that are visible in the schema. With annotations present, this is moderate added context.

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 a single, tightly worded sentence that front-loads the primary action and key differentiator. There is no redundant information, and every phrase contributes value.

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 tool with 9 parameters and a complex browser-related workflow, the description is minimal. The presence of an output schema and annotations helps, but it does not guide parameter selection or explain the tool's role relative to siblings, making it complete only at a basic level.

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?

The input schema provides 100% description coverage for all 9 parameters, so the description does not need to explain parameter details. The tool description adds no additional semantic meaning 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 clearly states the action ('Open a WeChat article URL') and the result ('return structured page status'), while the phrase 'without requiring full extraction' explicitly distinguishes it from the sibling tool wechat_read_article. This is a specific verb+resource+scope formulation.

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 'without requiring full extraction' implies a use case (checking status without full content) but does not explicitly name alternatives or state when not to use this tool. The guidance is present only implicitly, not as direct usage direction.

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