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

Annotations already establish readOnly/openWorld/non-destructive, and the description usefully adds pagination granularity (one month per page, cursor pages backward) and a cost warning that repeated requests may re-purchase data. But the cost disclosure is self-contradictory in the same paragraph: 'at least 10 Nexscope credits' versus '1 credit per request', which leaves the agent unable to predict spend. It also never clarifies whether url or handle should be supplied, despite both being optional.

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 text is bloated and concatenated from supplier boilerplate: 'Defaults to the current year' and 'returns one month at a time' each appear twice, and fragments like 'GitHub Activity API View Pricing', 'Actual supplier units are reported per request' and 'Examples are not guaranteed prices' are raw marketing/legal residue. The useful behavioral facts are buried in the middle rather than front-loaded, and two conflicting credit figures sit within a few lines of each other.

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?

With no output schema, the description does the right thing by mentioning the 'activity array' and month-sized pages, and it flags the credit cost. But it leaves an important ambiguity unresolved for a zero-required-parameter tool: url versus handle, and what happens if neither is given. The duplicated and contradictory pricing text weakens an otherwise adequate picture.

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 100%, so the schema already documents url, year, cursor and handle, and the description largely restates them ('Defaults to the current year', 'Pass cursor from the previous response to page backward'). It does add one thing the schema lacks: results arrive 'one month at a time in the activity array'. Baseline 3 applies since the schema carries the parameter burden.

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 opening sentence gives a specific verb and resource: 'Retrieves GitHub profile contribution activity for a user from the public profile activity timeline.' That is materially clearer than the title 'GitHub Activity'. However, it never distinguishes itself from the very close sibling social_github_user_contributions (or social_github_user), so an agent still has to guess which of the two contribution tools to pick.

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 guidance on when to prefer this over social_github_user_contributions or social_github_user, which is the single most likely selection mistake given the sibling set. The only conditional statement is 'Defaults to the current year when year is not provided', which is a schema default (and repeated in the schema itself), not usage guidance.

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