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

Annotations declare destructiveHint=true and readOnlyHint=false, so the safety profile is known. The description adds useful scope context beyond that — the call grants no room and no human authority, and it is legacy/unavailable in directory mode — but it never explains what the destructive action actually affects, leaving a gap against destructiveHint=true.

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?

Two short sentences, front-loaded with the identity of the endpoint and immediately followed by the availability restriction. Nothing is padded, though the phrase "no room or human authority is granted" is somewhat cryptic without context.

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 zero-parameter tool with no output schema, the description covers availability and authority limitations but never states what the endpoint does when it is available or what the caller observes on return. An agent can conclude it is probably not worth calling, but not fully why.

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 tool takes zero parameters, so there is no parameter semantics to document; the schema is empty and fully specified. Baseline 4 applies.

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 labels it a "Legacy operator-pairing confirmation endpoint," which names the resource (operator pairing) but the verb "confirmation" is vague about what actually happens on invocation. It does not explicitly distinguish itself from the sibling read_operator_consent, though the "Legacy" and "directory mode" framing hints at a deprecated variant.

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 gives one concrete when-not condition: "Unavailable in directory mode." That is real routing guidance, but it never names the alternative tool (read_operator_consent) or states whether there is any mode in which an agent should actually call this.

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