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

Beyond the idempotent and non-destructive annotations, it discloses login/auth context, the INTRODUCED quota shared with real group creation (10 per 24h, backfills count, read warning), and that mistaken records must be set to DEAD rather than deleted. It also states that outcome/reason become the user's original text ledger.

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 short and front-loaded with the action, then packs the important rules into compact semicolon-separated clauses. Every clause carries operational meaning, including the quota warning and no-delete correction rule.

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 batch mutation with a schema-covered parameter and no output schema, the description covers the key status, quota, warning, and deletion rules. The main missing piece is batch failure semantics, such as whether partial successes are possible or whether the list is atomic.

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%, so the schema already defines the array structure, matchId, patch fields, enum, and maxItems. The description adds useful semantics beyond that: the lifecycle statuses, the INTRODUCED quota implication, and the ledger meaning of outcome/reason.

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 and resource: batch-changing broker match status/outcome, recorded per item. It is clear what the tool does, but it does not explicitly distinguish this update path from siblings such as introduce_broker_match or create_broker_match.

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 implies usage for batch progress updates and for correcting mistaken matches by setting DEAD, and it mentions an INTRODUCED quota. However, it does not explicitly say when to use this tool instead of introduce_broker_match, create_broker_match, or other broker tools.

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