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

Annotations already declare destructiveHint=true, openWorldHint=true, and idempotentHint=false; the description adds real value by narrowing behavior to consent-only, internal (not external) outreach and by noting downstream opportunities require existing review. However, it never says what the 'destructive' aspect actually affects or why the call is non-idempotent, and 'no external outreach' sits uneasily next to openWorldHint=true without reconciliation.

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?

It is short and front-loaded, with no padding sentences. But the brevity is achieved through unexplained internal jargon ('FX', 'FIT', 'existing review'), so the compactness costs comprehension rather than buying clarity.

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?

This is a destructive, open-world mutation with three required, undocumented parameters and no output schema. The description gives no indication of what a successful call produces, what state changes, or what the agent should do next, which is inadequate for a tool at this complexity level.

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 0% and all three parameters are required, so the description carried the full explanatory burden and mentions none of them. intent_id and request_key (8-100 chars) are especially cryptic, and nothing explains how counterpart_id relates to consent or how request_key functions as an idempotency/dedup token.

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 leans on opaque jargon: 'Consent-only FX network discovery/handshake' and 'FIT creates internal opportunities requiring existing review' do not resolve into a concrete verb+resource an agent can reason about. It never distinguishes this tool from near-identical siblings such as respond_to_network_request, request_opportunity_match, or discover_network_intents, so selection remains guesswork.

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?

Phrases like 'no identity, contact, terms, documents or external outreach' imply scope limits, but they are stated as negations without saying when this tool is the right choice versus respond_to_network_request or request_opportunity_match. No prerequisites, ordering, or preconditions are given.

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