Ingest repo content

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

Discloses idempotency, single-commit behavior, and scope (tracked+non-ignored files, docs). No annotations exist, so description fully compensates.

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?

Three sentences with no fluff. Front-loaded with action, then consequences and usage advice.

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?

Complete for a side-effect tool: covers input, operation, idempotency, and use case. No output schema needed as write is the primary 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?

Schema covers 100% of parameters with good descriptions. Description adds context about how parameters relate to tool behavior (e.g., depth to tree), but doesn't detail each param.

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?

States specific verb 'scan' and resource 'git repo', enumerates outputs (overview, tree, docs). Distinguishes from siblings like memory_repo_info and memory_search.

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?

Explicitly advises 'Run this once when adopting a repo to seed memory', clearly indicating when to use. Sibling tool names provide alternative contexts.

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