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

No annotations are provided, so the description carries the full burden. It does disclose key behavioral traits: the response is an 'ordered list' and is not a time series, and the tool is 'lightweight.' Yet it does not explicitly state that the operation is read-only, nor does it mention authorization needs or rate limits. For a no-annotation tool, this is a moderate level of transparency.

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 exactly two sentences, with the primary purpose and key differentiator front-loaded ('ordered list of top entities for a slice -- no time series') and a secondary use case following. Every word earns its place, and it avoids restating schema 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 simple list-fetch tool, the description adequately captures what is returned (ordered list, no time series) and when to use it. The rich input schema and the presence of an output schema cover parameter and return details. It could mention that it uses the same query object as other analytical endpoints, but that is already documented in the schema and not essential for selection.

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 input schema has 100% description coverage, with detailed explanations for all parameters including the nested query object. The description itself adds no parameter-specific meaning beyond referring to 'a slice' and 'top entities,' so it stays at the baseline of relying on the schema for parameter semantics.

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 states that the tool returns an ordered list of top entities for a given slice, and explicitly notes it does not include a time series. It distinguishes itself by framing the use case as 'populating entity pickers' or 'quickly checking who the top partners/reporters are', which differentiates it from sibling tools that provide full series or detailed reports.

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 gives clear context for when to use it: 'for populating entity pickers or quickly checking who the top partners/reporters are without pulling full series.' This implies a lightweight alternative to full-series tools. However, it does not explicitly name sibling alternatives or state when not to use it, so it falls just short of full exclusion guidance.

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