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

No annotations are provided, so the description carries the full burden of behavioral disclosure. It mentions the kind of data (calls, successes, latency) but does not state whether the operation is read-only, whether it has side effects, or what the response structure looks like. This is insufficient for a tool with no annotation safety net.

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 a single concise sentence, which is efficient in length, but it is under-specified rather than appropriately concise. It does not provide enough content to be actionable, so the brevity works against it.

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 tool with two parameters and no output schema, the description should at least indicate the required agentId and optional days, and describe the expected return data. It does neither, so the agent lacks critical information to invoke the tool 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?

The schema has two parameters (agentId and days), but the description does not mention either one, their meaning, or constraints. With 0% schema description coverage, the description should compensate, but it provides no parameter-level information, leaving the agent to guess what 'days' refers to or how to format agentId.

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 indicates the tool reports on agent behavior metrics (calls, successes, latency) for real proxied traffic, which distinguishes it from other agent-related tools like agent_reputation or agent_attestations. It is not a tautology, but it lacks an explicit verb such as 'get' or 'retrieve', making the purpose slightly less direct.

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 description provides no guidance on when to use this tool versus alternatives. It does not mention required parameters, typical use cases, or exclusions. An agent cannot determine if this is the right tool for a given query without additional context.

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