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

Beyond the destructiveHint annotation, the description discloses important behavior: the expected count acts as a guard and nothing is written if the count has changed, write-access permission is required, and availability is gated by the company's AI plan. It also adds a human-confirmation workflow requirement.

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 purpose is front-loaded, and the description is compact with no wasted explanation. A few short permission/gating sentences are terse fragments rather than polished prose, but they remain informative and easy to scan.

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 destructive batch mutation with no output schema, the description covers the key invocation details: scope, source format relation, concurrency guard, permissions, plan gating, and human confirmation. It does not describe success responses or whether decisions are reversible, but it is otherwise complete enough to call the tool correctly.

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 schema already defines all five parameters. The description still adds semantic value for source and expected by linking source naming to list_persons and explaining that expected is a count guard that prevents writes when stale.

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: confirm or reject every PROPOSED person of one source at once, scoped to the persons found in one page/issue/comment. It also names the related sibling list_persons, so the agent can distinguish this batch decision tool from the listing tool.

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 gives clear usage context: it is a batch decision over proposed persons of a single source, and it says to ask the person first. It does not explicitly compare against alternatives such as individual person editing or merging, but the scope and prerequisites are clear enough for correct invocation.

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