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

Annotations already declare readOnlyHint, idempotentHint, non-destructive and openWorld, so safety is covered; the description adds genuinely useful behavioral content by enumerating what the payload contains (counts by field, pay rates, pricing, briefing page URL). It omits freshness/caching of the "live counts" and result size, but for a single-parameter read this is beyond the annotation baseline.

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 front-loads audience marketing copy ("For teams building AI who need expert human data") rather than the action, then packs one very long sentence with a parenthetical job-title list and a six-item clause chain. The information is relevant but padded — the roster of professions and the repeated "expert" framing could be cut without loss.

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-optional-param, no-output-schema read tool, the description is substantially complete: it spells out the categories of data returned and the optional field filter. Missing is how the returned data relates to sibling tools that also report pay and market data, which is the one real gap.

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 enum parameter is fully documented with examples in the schema, so the baseline of 3 applies. The description's only contribution is "Optionally one field," which restates the already-documented optionality without adding filtering semantics or scope implications.

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 uses a concrete verb family ("Returns what it delivers, the network's live counts by field, what each kind of expert is paid..., how projects are priced") and names the vendor, so an agent can tell this is a vendor-profile/data-lookup tool. It does not differentiate itself from siblings, and it overlaps visibly with get_ai_training_pay by claiming to return pay figures without explaining the split.

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 only usage signal is "For teams building AI who need expert human data" — that describes an audience, not a tool-selection condition. No when-to-use, when-not-to-use, or alternative is named, even though get_ai_training_pay and get_ai_training_market sit right beside it and plausibly cover the same questions.

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