Library Resolution Distribution

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

With zero annotations, the description must carry the full burden of disclosure. However, it provides no information about read-only nature, pagination behavior, or what data is summarized (e.g., per app or library-wide). The description is insufficient for an agent to understand the tool's effects.

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?

While extremely short (4 words), the description is under-specified rather than concise. It omits essential information, failing to earn its place. A good conciseness would include key details without verbosity.

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?

Given the complexity (11 parameters, 0 required, no output schema), the description is entirely inadequate. It does not cover what the tool returns, how to filter or paginate, or any edge cases. The agent cannot correctly invoke this tool.

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 11 parameters with 0% description coverage, and the description adds no explanation for any parameter. Agents have no way to infer the meaning of 'to', 'from', 'app', 'cursor', 'groupBy', etc., making the tool effectively unusable without external knowledge.

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 'Summarize resolution distribution' only vaguely states the action and resource. It does not specify what 'resolution' refers to (e.g., video resolution, something else) nor differentiate from sibling tools like 'resolution_distribution' or 'library_codec_distribution'.

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 guidance on when to use this tool versus alternatives. The description is too brief to indicate any context, prerequisites, or exclusions. With many distribution-related siblings, the lack of differentiation is a critical omission.

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