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

Annotations are empty, so the description must fully disclose behavioral traits. It does not state whether the tool is read-only, what it returns (e.g., pass/fail, detailed report), how failures are signaled, or any side effects. The verb 'Check' implies a non-mutating operation, but this is not explicit. With zero annotation support, the description leaves critical behavioral unknowns.

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 a single sentence and thus concise, but it tries to list many gate types without elaboration. The structure is acceptable, but the brevity comes at the cost of essential details. It is not overly verbose, but it is under-specified rather than optimally concise.

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?

Given the complexity of the tool (checking multiple gates) and the absence of both an output schema and any annotations, the description is severely incomplete. It does not explain the expected payload structure, the response format, or the implications of passing/failing a gate. An agent cannot reliably invoke this tool without additional undocumented assumptions.

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 only parameter 'payload' is a generic object with no defined sub-properties and 0% schema description coverage. The description never explains what should be included in the payload, leaving the agent completely in the dark about the required input structure. Since the tool's entire input is this opaque payload, the description fails catastrophically to compensate for the schema gap.

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 clearly states the tool's function: checking multiple gate conditions (approval, attribution, duplicate/collision, consent, eligibility, compliance) before a handoff. It uses a specific verb 'Check' and names the resource context (referral/partner-program), which distinguishes it from generic utilities. However, it overlaps conceptually with sibling gate tools like personalization_evidence_gate, so it doesn't fully differentiate itself.

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 provides a temporal context ('before an introduction or lead handoff'), implying when to use it. However, it does not mention any alternatives, exclusions, or conditions for when not to use it. While the purpose suggests it's a prerequisite gate check, there's no explicit guidance on choosing it over sibling tools that may also perform checks.

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