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

With no annotations, the description carries the full burden, and it does disclose one meaningful trait: 'counts only, no personal data', which tells the agent results are aggregated and safe to surface. It says nothing about permissions, rate limits, data freshness, or caching, which matters for a stats endpoint an agent may poll.

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 sentences, zero filler: the first front-loads the privacy guarantee and enumerates the returned metrics, the second gives the use case. Nothing could be removed without losing information.

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?

There is no output schema, but the description effectively substitutes for one by listing every metric returned, including the verified/unverified split and the status breakdown for job requests. The only gap is the response shape (field names, whether counts are nested), which an agent must discover by calling.

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 and the schema is an empty object, so there is nothing to disambiguate; the baseline of 4 applies. The description adds no parameter-level noise.

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?

States a specific verb ('Counts') and enumerates exactly what is counted: total listings (verified/unverified), total searches, total job requests by status, and recent timestamps. This clearly separates it from the action-oriented siblings (get_listing, search_pros, send_job_request), though it never names them explicitly.

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?

'Use this to check whether the network is being used' gives a concrete selection context, and no sibling offers aggregate metrics, so the choice is unambiguous in practice. It does not state when not to use it or what to use for per-record inspection.

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