resolve_repo

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

Discloses remote reading order (upstream, origin, other), error behavior ('Errors if no parseable remote'), and that all discovered remotes are returned. No annotations provided, so description carries full burden. Does not detail return format beyond 'all discovered remotes'.

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?

Two efficient sentences with zero redundancy. Purpose is front-loaded, each clause adds value.

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 simple tool (1 optional param, no output schema), the description covers purpose, behavior, error case, and usage recommendation. Fully adequate for agent invocation.

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 baseline 3. Description adds that 'path defaults to the current directory', which is a meaningful behavioral detail beyond the schema's description.

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 'Detect' and resource 'baseUrl/owner/repo from git remotes', and specifies remote priority order. It distinguishes from siblings which are all issue/label CRUD tools, making this a setup tool.

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 says 'Call ONCE at the start of a session to establish owner/repo for later calls instead of guessing', providing clear usage context. No explicit when-not-to-use but the sibling tools imply this is a prerequisite.

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