Git for me!

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

With no annotations, the description carries full behavioral burden and does disclose meaningful traits: the tool may return questions rather than act, "unknown" is an acceptable answer, and it returns a method rather than performing the search itself (delegated to git_for_me_search). It stops short of describing exact output shape, but the two-phase behavior is well conveyed.

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?

Front-loaded with the sequencing cue ('Step 1 of 3'), and every clause contributes to the workflow. It is dense and slightly run-on in the middle, but there is minimal filler.

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?

No annotations or output schema exist, so the description must explain return behavior — and it does, stating it returns either questions or a method. For a 5-parameter orchestration tool this is largely complete, though the precise structure of the returned method is only sketched.

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%, so all five parameters are already documented, establishing a baseline of 3. The description adds real value by explaining that the four optional fields may be omitted and that 'unknown' is a valid response, giving an agent guidance the schema alone does not provide.

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 states this is "Step 1 of 3" of a workflow that gathers requirements before recommending a repo, and that it returns intake questions or a build/search method. It distinguishes itself from siblings by naming git_for_me_search as the tool it hands off to. The specific verb ('returns the questions' / 'returns the method') is present but somewhat buried in workflow prose.

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 states the trigger condition ('before recommending any open-source repo or writing something that might already exist') and the fallback behavior ('If stack, platform, license or upkeep is missing, returns the questions to ask the user first: call again with the answers'). It also names the sibling to use next. Nothing about when to invoke is left to inference.

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