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

The description discloses login requirements, a concrete side effect (INTRODUCED consumes the shared 24-hour group-introduction quota of 10), a response warning, and operational policies such as not deleting erroneous matches and marking them DEAD instead. It adds significant behavior beyond the annotations and does not contradict readOnlyHint, idempotentHint, or destructiveHint.

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 dense but structured into login, workflow, and policy sections, with the most critical quota warning highlighted. It is longer than strictly necessary — for example, the App-button contextual detail is peripheral — but every section still earns its place.

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 mutating tool with no output schema, it covers the essential operational context: auth, workflow, status semantics, quota side effects, and the response warning. The main gaps are the under-defined 'reason' field and the lack of a broader response or error description.

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 description maps status enums to human meanings, explains that outcome is free text unavailable in the App, and notes that outcome/reason are stored and returned verbatim. It does not fully define the meaning of 'reason', and nested patch fields lack schema descriptions, so the description only partially compensates.

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 opens with a specific action: batch-change broker-match status and write a free-text outcome, then lists all five statuses with Chinese labels. This is clear about the resource and operation, but it does not explicitly name a sibling alternative such as introduce_broker_match, so differentiation is implied rather than stated.

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 '组合链' section gives an explicit workflow: pull follow-ups from get_broker_desk, ask the user about each match, then call this tool once with updates. This is strong when-to-use context, but it does not state exclusions or when to prefer an alternative tool.

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