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

With no annotations provided, the description carries the behavioral disclosure burden. It does disclose key behavior: results are shares computed over scored providers with explicit denominators, and this is an aggregated read-style operation. Still, it does not mention output structure, pagination behavior, or any side effects/limitations, leaving meaningful gaps.

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?

The description is short and front-loads the core metric semantics before giving the motivating use case. The 'INFLUENCE — diffusion:' prefix is slightly cryptic and not obviously useful, but overall every substantive clause earns its place.

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 simple parameter-light aggregation tool, the description is adequate for an initial call: it explains the core output and the value of the denominator. However, with no output schema and no annotations, it leaves unclear how pagination applies or what a returned row looks like, so it is only minimally complete.

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 only 33%, and the tool description adds no explanation for page, limit, or context. The context parameter is well described in the schema itself, but page and limit semantics are left entirely to inference, and the description does not compensate for that 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 description clearly defines the tool's output: for each agent-readiness dimension, the count and share of scored providers that satisfy it, with an explicit denominator. It is specific about the resource and metric, though it relies on the name to identify the verb and does not explicitly distinguish itself from sibling tools.

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 last sentence implies a use case: this supplies the denominator needed to support claims that 'the agent web is/is not here yet.' However, it offers no explicit guidance on when to choose this tool over siblings like get_agent_readiness or readiness_gates, and no when-not-to-use conditions.

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