github_activity_list_watchers_for_repo

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

No annotations are present, and the description does not disclose any behavioral traits such as pagination behavior, rate limits, or what data is returned. The input schema includes pagination parameters, but the description does not mention that the results are paginated or any other side effects.

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 concise at two words, which is efficient but lacks front-loading of key information. It does not provide any structure or additional details that would help an agent quickly understand the tool's scope.

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 absence of an output schema and annotations, the description should compensate by explaining what a 'watcher' is and what the return values look like. The description is too minimal to be considered complete, especially when compared to sibling tools that have longer descriptions.

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 input schema has 100% description coverage for all four parameters (owner, repo, per_page, page). The descriptions in the schema are sufficient to explain each parameter's meaning. The tool description adds no additional value beyond the schema, hence baseline 3.

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 'List watchers' combined with the tool name 'github_activity_list_watchers_for_repo' clearly indicates the action (list) and the resource (watchers for a repo). It distinguishes from siblings like github_activity_list_stargazers_for_repo as watchers and stargazers are different concepts.

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 guidance is provided on when to use this tool versus alternatives. For instance, there is no clarification on the difference between watchers and stargazers or when to use list_watchers_for_repo vs list_stargazers_for_repo. The description lacks any usage context.

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