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

Annotations already declare readOnly/idempotent/openWorld/non-destructive, and the description layers on real context beyond them: a login requirement ('需要登录'), the 20-item cap, that scripts contain no contact details, and that a genuine intro consumes a 24h group-creation quota. These are non-obvious operational constraints an agent needs.

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 content is compressed into one long semicolon-chained run-on. It leads with the login tag rather than the tool's purpose, and the embedded downstream-tool instructions (introduce_broker_match, update_broker_match) compete with the tool's own semantics.

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?

With no output schema, the description does describe the return payload (intro scripts, max 20, no contact info) and the surrounding broker workflow, which is substantial. However, the dangling bothPlatform reference leaves a genuine ambiguity about how to invoke the tool for the in-site group path.

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% for the single matchIds parameter, so the baseline would be 3, but the description adds no meaning for matchIds while introducing 'bothPlatform=true', a parameter absent from the schema. This mismatched reference risks the agent hallucinating an argument.

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 it returns up to 20 intro scripts for matchmaking ('最多20条撮合的介绍文案，无联系方式'), which is a recognizable resource. However, it never cleanly distinguishes itself from neighboring broker tools such as collect_broker_leads, get_broker_desk, or scan_broker_matches, so an agent must still infer which retrieval tool applies.

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 offers conditional workflow guidance (off-platform scripts must be sent by the user, 'bothPlatform=true' enables in-site group creation via introduce_broker_match), which is useful context. But the pivotal condition references a bothPlatform flag that does not exist in this tool's schema, so the when-to-use branch is not actionable as written.

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