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

Goes well beyond the annotations (readOnlyHint=false, idempotentHint=false, openWorldHint=false) by disclosing the one-time nature and 24-hour validity window, plus the downstream side effect: a paired recipient becomes visible in list_recipients and emits a `paired` event with email and connection_id. That tells the agent exactly what state this mutating call creates and how to verify it.

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 core fact is front-loaded, but the body is one long run-on sentence stitched together with em-dashes and nested parentheticals, which makes the pairing flow harder to scan than it needs to be. A short numbered breakdown of the three ways to pair would convey the same content more efficiently.

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 one-parameter, no-output-schema tool, the description covers the full lifecycle: what is returned (code, link, QR), how the recipient consumes it, and how the agent confirms pairing afterwards. Nothing an agent needs before or after calling is missing.

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% and the single agent_id parameter is already documented in the schema as coming from list_agents or create_agent. The description adds no further detail about the parameter itself, so the baseline 3 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?

States a specific artifact — a one-time pairing code valid 24 hours, delivered with a link and QR code — and immediately frames its purpose (letting someone receive this Agent's requests). An agent can distinguish this from siblings like create_agent or list_recipients without opening the schema.

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?

Explains the concrete usage path: hand the code to the person, who scans the QR, opens the link, or types the code into Taskriz (+ → Pair an Agent). It also states the post-condition to watch for (they appear in list_recipients and a `paired` event in get_replies). It stops short of explicit when-not-to-use guidance, but no obvious alternative tool exists for this capability.

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