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

readOnlyHint=true already covers the safety profile. The description adds real context beyond that: results are aggregated (not raw request rows) and ranked by frequency of absence of a verified provider. It omits anything about the time window, aggregation granularity, or how counts are computed.

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?

One compact sentence with no waste and the ranking criterion front-loaded. It is slightly elliptical ('Aggregated requests agents made') but nothing could be cut 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?

For a one-optional-param read-only tool with no output schema, the description conveys the core concept. However, with no output schema and no schema param docs, the unexplained `days` window and unspecified aggregation granularity leave genuine ambiguity about what the returned numbers mean.

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 single parameter `days` has 0% schema description coverage, so the description is the only place meaning could be supplied — and it says nothing about it, neither its default horizon nor whether it filters the request timestamps or the ranking period. This is a clear compensation gap.

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 sentence names a specific resource (aggregated agent requests) and its ranking dimension (how often no verified provider existed), which is meaningful and distinct from siblings like ventru_usage or ventru_search_providers. It is a noun phrase rather than an explicit verb+resource, but the reporting/read intent and scope are recoverable without opening the schema.

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?

No usage guidance is given: nothing says when to pick this over ventru_usage or ventru_find, or what question this answers. The agent must infer that this is for spotting supply gaps rather than for individual provider lookups.

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