memory_git_connect

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

Annotations already declare idempotentHint=true, indicating safe re-runs. The description adds that it sets up automatic syncing of commits and PRs, but lacks details on authentication, permission requirements, or behavior if a connection already exists. Beyond annotations, the additional behavioral context is minimal.

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?

Single sentence of 13 words, directly stating the tool's function with no filler. Front-loaded with action and purpose. Highly efficient.

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 the basic functionality but omits details like return value (no output schema), error scenarios, or idempotency (though annotations cover it). For a simple setup tool with two required parameters, the description is minimally adequate but leaves gaps for an agent needing full context.

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?

Input schema documents both parameters with descriptions (100% coverage). The tool description adds no further information about the parameters, such as validation rules, format examples, or relationship between them. Baseline score of 3 is appropriate given full schema coverage.

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 the verb 'connect', the resource 'GitHub repository', and the purpose 'to automatically sync commits and PRs to memory'. It distinctly separates this tool from siblings like memory_git_disconnect, memory_git_sync, and memory_git_list by focusing on the initial connection setup.

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 when to use this tool (to set up automatic syncing) but provides no explicit guidance on prerequisites, alternative tools, or when not to use it. For example, it does not mention that memory_git_activate might be needed first or that memory_git_sync is for manual syncs.

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