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

With no annotations, the description carries the burden. It discloses that the tool sets or updates the remote and explains token requirements for private repos. However, it does not mention whether the operation overwrites an existing remote, prerequisites like an initialized Git repo, or potential side effects, leaving some ambiguity for a mutation tool.

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?

The description is two sentences, front-loaded with the action, and every word earns its place. It efficiently conveys the core functionality and the main variation (token for private repos) without repetition.

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 straightforward remote-configuration tool, the description covers the essential purpose and key nuance (token for private repos). The schema covers all parameters and no output schema exists, so the description is reasonably complete. However, it could include a brief note about overwriting behavior or when to use git_info instead, but these are minor gaps.

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 description coverage is 100%, so the schema fully documents all four parameters. The description adds marginal clarification about token use (public vs. private) but does not provide significant new meaning beyond the schema fields.

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 'Set or update the upstream Git remote (GitHub/GitLab) for an app', using a specific verb and resource. It distinguishes from siblings like remove_git_remote and git_pull by indicating this is specifically for configuring the remote source.

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?

Provides clear context on when to use the tool (setting/updating remote) and notes public vs. private repo token requirements. However, it does not explicitly state when not to use it or name alternative tools for similar operations.

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