repo_add_remote

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

No annotations are provided, so the description carries the full burden of behavioral disclosure. 'Add' implies a mutation, but the description does not mention side effects, required permissions, or conditions such as whether the remote must not already exist. This is a significant transparency gap for a tool that modifies repository state.

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 a single, concise sentence that directly conveys the tool's purpose without any redundant words or filler. It is appropriately sized for a simple operation and adheres to the principle of front-loading the essential information.

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 that the tool mutates state, has no annotations, and has an output schema, the description is too minimal. It does not explain what the output represents, any preconditions (e.g., the repository must exist), or how this tool relates to siblings like 'repo_setup_remotes'. The description leaves the agent with questions about expected behavior and prerequisites.

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 input schema has 0% coverage (no descriptions for parameters) and the description does not compensate. The description 'Add a new remote to the repository' provides no additional meaning for 'workspace_id', 'name', or 'url'. Without any guidance, the agent cannot understand the purpose or constraints of each parameter, especially 'workspace_id'.

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 'Add a new remote to the repository' clearly states the verb and resource, making the tool's function immediately understandable. However, it does not explicitly differentiate itself from the sibling tool 'repo_setup_remotes', which could imply a similar or overlapping functionality.

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 description provides no guidance on when to use this tool versus alternatives, nor does it mention any prerequisites or context. It is a single imperative sentence with no conditionality or exclusion criteria.

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