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

With no annotations, the description carries the full behavioral burden, yet it never states that the call is read-only, side-effect free, or unauthenticated. The fee and referral-policy sentences describe business rules (Doing Work never charges lead fees, never sets a price) rather than the tool's runtime behavior, so the agent learns marketing context but not operational traits.

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 information scope. The second sentence is arguably helpful domain context rather than filler, though it reads slightly like promotional copy that a terse definition could compress.

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-argument informational tool with an output schema that documents return values, the description covers what topics the response addresses. It still omits whether the call is safe/read-only and when an agent should reach for it, which leaves meaningful gaps given there are no annotations to fall back on.

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 the baseline is 4; there are no argument semantics the description could add value on. The schema coverage of 100% is moot with an empty properties object.

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 names the resource (the customer quote network) and enumerates the content it returns (area, trades, rules), which distinguishes it from siblings like network_listingGet or network_inbox. However, it is phrased as a noun clause rather than a verb+resource statement, so it never explicitly says the tool 'returns' or 'describes' anything. The intent is inferable but not stated.

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 guidance on when to call this versus alternatives such as network_listingGet, network_inbox, or legal_shopTerms, nor any preconditions. The agent must infer that this is the entry point for learning about the network's scope and fee policy.

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