Audio Distribution

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

Absent annotations, the description carries the full burden of behavioral disclosure. The single sentence only states the counting purpose, omitting critical details like read-only nature, pagination, parameter effects, or output format.

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 concise at one sentence, but it is too terse for a tool with 11 parameters and no schema descriptions. It adequately states the purpose but leaves significant gaps.

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 tool's complexity (11 parameters, no annotations, no output schema), the description is highly incomplete. It does not cover parameter semantics, pagination, grouping, or return values.

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?

With 0% schema description coverage and 11 parameters, the description fails to add any meaning beyond the parameter names. No parameter details are provided, leaving the agent to guess their roles.

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 'Count library items by audio codec' clearly states a specific verb, resource, and scope. However, it does not differentiate from sibling tools like 'codec_distribution' or 'library_audio_distribution', which may have overlapping functionality.

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, nor any prerequisites or exclusion criteria. The agent receives no context for decision-making.

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