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

Beyond the readOnly/idempotent annotations, it discloses an unusual cost model (1 unit for ≤10 items, 2 for 11–20; 5/10 units for keyword queries, including empty results), pagination behavior via cursor, a prompt-injection warning that titles/summaries/conditions are untrusted data, and that reading never earns Credit. These are exactly the behavioral facts an agent cannot get from the annotations.

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 front-loaded with the purpose and then packs cost, pagination, and safety into a tight sequence with no filler. It is dense but each sentence carries actionable content; only the participation-guide mention feels slightly underdeveloped rather than wasteful.

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?

With an output schema present, return values need not be described, and the description covers cost, pagination, filtering defaults, and untrusted-data handling. The remaining gap is the unexplained role/reward/category filters, which an agent may need to use correctly.

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% across 7 parameters, so the description must compensate. It explains limit (item-count cost tiers), query (keyword cost), cursor (continuation on empty pages) and recruitment (ALL for history), but role, reward, and category are never mentioned, leaving nearly half the surface undocumented in both places.

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 gives a specific verb and resource ('Discover public Network Mission opportunities') and lists the fields returned (recruitment/reward conditions, participation-guide reference). It is clear about what the tool does, but never names a sibling to distinguish it from, so an agent must infer the boundary with search_network or get_network_item.

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?

It gives concrete situational guidance: when current recruitment results are empty, switch to recruitment ALL and continue the cursor, which is a real when-to-use rule. It also explains the cost trade-off between browsing and keyword queries, which steers query strategy. It stops short of explicitly routing the agent away from alternatives.

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