resolve_repo

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

Fully describes behavior: reads upstream first, then origin, then any other remote; returns all discovered remotes; defaults path to current directory; errors if no parseable remote. No annotations exist to supplement, so description covers everything.

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: action, reading order, usage recommendation, error behavior. All information is front-loaded and no wasted words.

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?

For a simple tool with one optional parameter and no output schema, the description covers detection method, order, default, error case, and usage context. It is complete for the agent to understand when and how to invoke.

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% and the description adds the note about path defaulting to current directory, which is already in the schema. However, it provides context on how the parameter interacts with the overall behavior (remote detection), so it's adequate but not extra.

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?

Clearly states the action: detect baseUrl/owner/repo from git remotes. The verb 'detect' and the resource (owner/repo from remotes) are specific. It distinguishes itself from siblings as a setup tool for establishing context.

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 to call once at session start to establish owner/repo instead of guessing. It also describes the fallback order (upstream, origin, any other) and error case, providing clear when and how to use.

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