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

Annotations already declare readOnlyHint=true, idempotentHint=true and destructiveHint=false, so the safety profile is covered. The description adds a consent-only constraint, but the closing sentence 'FIT creates internal opportunities requiring existing review' is opaque and never explains the return payload or whether any internal record is touched.

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, but it is front-loaded with policy jargon rather than the action, so the first thing an agent reads does not tell it what the call returns. Not verbose, just misordered.

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?

No output schema exists, so the description should explain what comes back, but it does not. Combined with an undocumented required ID, an agent cannot reliably form or interpret this call from the definition alone.

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?

There is one required parameter, request_id, with 0% schema description coverage and no title or description in the schema. The description says nothing about the identifier — where it comes from, its format, or how to obtain it — so an agent has no guidance beyond the field name.

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 name says get_network_request, but the description never says what the tool does: no verb like 'retrieve' or 'fetch', and no mention of returning a network request record. Instead it reads as policy text about consent and handshake rules, leaving the actual action unstated.

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?

There is no indication of when to call this instead of list_network_requests, get_agent_conversation, or respond_to_network_request. The exclusions ('No identity, contact, terms, documents or external outreach') describe data boundaries, not tool-selection criteria.

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