repo_monitor

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

Given no annotations, the description carries full burden and discloses key behaviors: actions, side effects (check updates watermark and dedups seenShas), and special behavior for reset with sinceDate. It lacks details on error cases, permissions, or performance, but covers the main operational traits.

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 well-structured with sections for actions, scope, and examples. It front-loads the purpose. While it could be slightly more concise, the examples provide clarity that likely aids understanding without excessive verbosity.

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?

The description covers all actions and parameters comprehensively, but lacks information about return values or expected output format. Since there is no output schema, the description could benefit from briefly summarizing what each action returns (e.g., status outputs). This gap limits completeness for a monitoring tool.

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 coverage is 100%, but the description adds valuable context: explains action enum in prose, clarifies the mutual exclusivity of name and module, and describes label and sinceDate in the context of the reset action. This goes beyond the schema's property descriptions.

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 clearly identifies the tool as a unified repository monitoring tool with three specific actions (status, check, reset) and distinct scope options. It differentiates from sibling tools like impact_analysis or repo_clone by focusing on monitoring and watermark management.

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?

The description provides explicit usage context for each action and scope (name or module) and includes concrete examples for cron scheduling and agile reset. It does not explicitly state when not to use the tool, but the action descriptions make the appropriate use cases clear.

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