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

With annotations already covering read-only and idempotent behavior, the description adds useful context beyond annotations: it says results come from the ATC leaderboard, include caller/timestamp/direction/result, and are ordered newest first. It does not mention pagination or limit behavior, which keeps it from a 5.

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 tightly packed sentence with no wasted text, and the most important information — what the tool returns and ordering — is front-loaded.

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?

The description covers return fields and ordering despite there being no output schema, which is helpful. However, it omits the date-range filtering behavior and limit semantics, leaving meaningful gaps for a tool with four parameters and low schema description coverage.

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 25%, with only the required asset parameter documented. The description does not explain the from/to date parameters or the limit parameter, so it fails to compensate for the schema coverage 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 states a specific resource and query: callers of an asset on ATC, including timestamp, direction, and result. It is clear what the tool returns, but it does not explicitly distinguish itself from sibling tools such as speaker_calls or calls_leaderboard.

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 implies the basic use case (calls involving an asset), but it gives no explicit guidance on when to choose this tool over siblings like speaker_calls or calls_leaderboard, and no exclusions or prerequisites are stated.

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