commit_activity

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

With no annotations, the description carries the full behavioral burden. It implies a read-only operation and lists returned content, but says nothing about auth/permissions, rate limits, whether activity spans all branches, or how the day window is truncated — and the return listing is already covered by the output schema.

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?

Two short sentences, purpose front-loaded ahead of the return breakdown. No filler; every clause carries 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?

An output schema exists, so return values need not be re-explained here, and the low-complexity read scope is clear. The definition remains incomplete on usage routing versus siblings and on behavioral characteristics, which no annotations supply.

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%, so the description must compensate. It clarifies the 'days' window ('last N days') which maps to the days parameter, and owner/repo are self-evident from the 'for a repo' framing, but the default of 30 and any format expectations are left unstated.

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 states a specific resource (commit activity for a repo) and a temporal scope (last N days), and enumerates the outputs (totals, per-ISO-week buckets, top authors, latest commit). It does not, however, differentiate itself from siblings such as contributor_stats, which also surfaces authorship, or repo_overview.

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 explicit when-to-use guidance, no when-not-to-use, and no mention of the sibling alternatives (contributor_stats, repo_overview). The temporal scoping implies a 'recent activity' use case but leaves the agent to infer when this tool is the right pick.

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