Repository activity

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

With no annotations and no output schema, the description carries the full behavioral burden, yet it only names the categories aggregated. It does not disclose whether results are counts or breakdowns, whether the window is inclusive, or what happens for repos with no activity. "Recent period" is also vague against a days parameter with a 7-day default.

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?

A single compact sentence front-loads the verb and resource, and every clause carries information about what is summarized. It is efficient, though it is short at the expense of the details an agent actually needs.

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 read-only aggregation the description covers the essential 'what,' but with no annotations and no output schema the agent has no sense of the return shape or the time-window semantics. The missing pieces are moderate rather than severe given the tool's low complexity.

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 0% across all three parameters, so the description must compensate and largely fails to. "Over a recent period" loosely gestures at the days parameter but never names it, cites its default (7), or explains the 1–90 bound; owner and repo receive no clarification beyond their self-evident names.

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?

States a specific verb ("summarizes") over a concrete resource set (issues opened/closed, PRs merged) with a time scope, which is clearly distinguishable from the item-level siblings list_issues/get_issue. It stops short of naming those siblings or contrasting itself with them, so the differentiation is implicit rather than explicit.

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?

There is no when-to-use guidance at all – nothing says to prefer this over list_issues or search_issues when the agent wants aggregate counts rather than individual items. The only contextual hint is the vague phrase "over a recent period," which leaves the selection decision to inference.

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