get_user_activities

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

Discloses that repo_stars returns cumulative counts, not per-period deltas, which is critical behavioral information beyond annotations. No contradictions with readOnlyHint.

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 concise sentences with front-loaded purpose. Every sentence adds value: purpose and a behavioral caveat. No waste.

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 output schema exists, description need not detail return values. Covers filtering, date formats, and star delta caveat. Missing description for username and max_results, but overall adequate.

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 coverage, description explains org, repo, since/until (including accepted date formats). However, username (required) and max_results are not described, leaving gaps.

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?

Clearly states 'Get user activities' with optional filtering by org, repo, and date range. Verb and resource are specific. Distinguishes from siblings like get_repo_stars_since by focusing on activities broadly.

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?

Provides usage context: when to use filters and date formats. Lacks explicit guidance on when not to use this tool vs alternatives, though the repo_stars caveat helps avoid misuse.

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