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

Even with annotations already marking this as read-only, idempotent, and non-destructive, the description adds meaningful behavioral context: login is required, the platform does not send messages, results contain no contact information, and the follow-up update_broker_match consumes daily quota. These details go well beyond the structured annotations.

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 front-loaded with the core purpose and limit, then organized into clear sections for the workflow and the bothPlatform distinction. It is moderately dense but every sentence adds useful context; the rationale about why the user must send from their own WeChat is slightly verbose but still informative.

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 one well-documented parameter and strong annotations, the description covers purpose, workflow, behavioral constraints, and the relationship to sibling tools. It does not describe the exact return structure, but for a simple batch-get tool without an output schema this is a minor gap, not a correctness blocker.

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%, so the single matchIds parameter is already documented with its type, min/max, and meaning. The description only repeats the limit of 20 and references the broader workflow, but adds no extra semantic detail about how matchIds are obtained or what format they take. Baseline 3 is appropriate.

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 action ('批量拿撮合的介绍话术') with a clear resource (broker intro scripts) and an explicit batch limit of 20. It also distinguishes itself from the sibling introduce_broker_match by explaining which matches can use that alternative, so an agent can differentiate the tools without opening schemas.

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 description provides an explicit workflow chain (create_broker_match → get_broker_intro_scripts → rewrite → user sends → update_broker_match) and gives clear when-to-use guidance via the bothPlatform distinction: bothPlatform=true matches may use introduce_broker_match, while false matches can only go through manual sending. It also states the prerequisite of login.

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