git_remote_info

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

With no annotations, the description carries the full burden and does meaningful work: it declares the operation read-only and, more valuably, discloses that credentials embedded in remote URLs are masked in the output. It stops short of covering failure behavior (non-git path, missing repo) which would have pushed it to a 5.

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?

One sentence, front-loaded with the resource and action, with the safety and masking notes appended compactly. Nothing is redundant or padding.

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 one-parameter read tool with an output schema (so return values need no explanation), the description covers purpose, safety profile, and output sanitization. The remaining gap is the unspecified `repo` path semantics, which is minor but real.

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?

The single `repo` parameter has 0% schema description coverage, so the description must compensate and it does not mention the parameter at all. An agent gets no clarification on whether `repo` is a path relative to cwd, a worktree root, or what the default '.' resolves against.

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 a specific verb and resource ('List configured remotes and their URLs') with an explicit scope qualifier ('read-only'). No sibling in the provided list covers git remotes, so an agent can select it unambiguously without opening the schema.

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 '(read-only)' tag implies this is a safe inspection call, but there is no explicit guidance on when to reach for it versus inspection siblings like git_status, git_branch_list, or git_log, and no prerequisites such as 'repo must be a git working tree' are stated.

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