Save Git Config

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

Annotations already indicate this is a write operation (readOnlyHint false, idempotentHint false). The description adds that it saves/updates provider, repo, and credentials, which is useful but does not disclose side effects, auth requirements, or whether it overwrites existing config. It provides some added context beyond annotations without rich behavioral detail.

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 front-loads the action and includes the key object. It avoids redundancy and is appropriately sized for the tool's simplicity.

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?

The description is adequate but leaves out the full scope of configurable parameters (e.g., branch, environments, base_url) and does not explain what happens on success/failure. With no output schema, the description could more fully explain the effect of saving config, but the schema covers parameter details.

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 100% coverage for all 8 parameters with meaningful descriptions. The tool description mentions only provider, repo, and credentials, but this does not add significant meaning beyond what the schema already provides. The baseline of 3 applies because schema handles parameter documentation.

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 uses a specific verb phrase 'Save or update' and clearly identifies the resource as 'git connection (provider, repo, credentials)' for an agent. This distinguishes it from sibling git tools like lyzr_git_init_repo or lyzr_git_get_status.

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 minimal context ('for an agent') but offers no guidance on when to use this tool versus alternatives. It does not mention exclusions, prerequisites, or why one might choose this over related tools like lyzr_git_validate_config or lyzr_git_disconnect.

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