memory_git_activate

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

Annotations already declare the tool as idempotent and non-destructive, which aligns with toggling a webhook. The description adds the context that it operates on a webhook after setup, but does not disclose additional behaviors like authentication requirements or error scenarios.

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 a single sentence that is concise and to the point, with no unnecessary words or repetition. It effectively conveys the tool's purpose with minimal fluff.

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 tool's simplicity (toggle a webhook), the description is largely complete. It lacks context about prerequisites (e.g., repository must be connected) and what happens if the webhook isn't set up, but the annotations provide safety cues. Overall, it's sufficient for an agent to understand the core action.

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?

All three parameters are fully described in the input schema (100% coverage). The description does not add any extra semantic meaning beyond what is already in the schema, so it meets the baseline of 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 clearly states it activates or deactivates a connected repository webhook after setup. It specifies the verb (activate/deactivate) and resource (webhook), and it distinguishes itself from sibling tools like memory_git_connect (which handles initial setup) and memory_git_disconnect.

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 implies usage after setup, but does not explicitly specify when to use this tool versus alternatives like memory_git_connect or memory_git_disconnect. No exclusions or prerequisites are mentioned, leaving some ambiguity.

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