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

Annotations already declare readOnlyHint=true, destructiveHint=false and openWorldHint=false, so the safety profile is fully covered. The description's "Read-only" sentence is redundant with those annotations; beyond that it usefully scopes what is counted (e.g. dedup-queue pairs and staged member changes), but adds no further behavioral context such as performance characteristics or freshness.

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 a single front-loaded sentence that begins with the core purpose and then enumerates the counted categories. The enumeration is long but every clause names a distinct aggregate, so it earns its place; a slightly more structured list format could improve readability.

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 read-only aggregate tool with one fully documented parameter and an output schema, the description provides enough context to know what will be counted. It is nearly complete; a brief note on scope (e.g. that counts are for the given company's network) would close the remaining 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?

There is only one parameter (companyId) and schema description coverage is 100%, so the schema fully documents it. The description does not mention the parameter at all; baseline 3 applies when the schema carries the parameter semantics.

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 opens with a specific verb ("Counts") and resource scope ("across the network") and then enumerates exactly which aggregates are returned — people with contact details, relationship-named counts, never-target counts, companies, firms, groups, events, investments, dedup-queue pairs and staged changes. This makes it clearly distinguishable from list-oriented siblings such as fundraising_list_network_people or fundraising_get_network_graph, which return entities rather than aggregate counts.

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?

Usage is implied: if you need aggregate counts rather than entity lists, this is the tool. However, the description never explicitly states when to prefer this over siblings like fundraising_get_fundraising_analytics or the various network list tools, nor does it mention any exclusions or prerequisites.

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