Average Release Size

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

No behavioral traits are disclosed. The description does not state whether the operation is read-only, whether it requires authentication, or any side effects. With zero annotations, the burden is entirely on the description, which completely fails to address this.

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 extremely short but at the cost of missing essential information. It does not achieve conciseness; it is under-specified. Every sentence should earn its place, but here one vague sentence is insufficient.

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 has 11 parameters, no output schema, and no annotations, the description is grossly inadequate. It fails to cover return format, parameter explanations, or any usage context, leaving the agent with almost no actionable information.

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 description provides no guidance on any of the 11 parameters. Schema description coverage is 0%, so the agent has no help understanding the meaning or usage of parameters like 'to', 'app', 'from', 'detail', 'groupBy', etc.

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 'Average release size from history data' adds minimal context beyond the tool name. It is a noun phrase, not an action, and fails to specify what kind of history data or how the average is computed. While not completely tautological, it is vague and does not differentiate from siblings like 'grabs_by_indexer' or '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 usage guidelines are provided. The description gives no indication of when to use this tool versus alternatives, no prerequisites, nor any exclusion criteria. The agent is left without context to decide appropriateness.

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