add_config_source

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

Describes supported git servers but omits side effects like overwriting existing sources, authentication needs, or idempotency. No annotations provided, so description should offer more behavioral context.

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 sentences, front-loaded with key purpose, no verbose or redundant text. Highly efficient.

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?

Despite having an output schema, the description lacks essential usage guidance for all 7 parameters. Without parameter descriptions or behavioral details, completeness is inadequate.

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 has 0% description coverage, and the description adds no parameter details. With 7 parameters, agents need guidance on fields like 'token_env', 'branch', 'priority'—none provided.

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 'Register a git repository as a config source,' specifying the action and resource. It differentiates itself from siblings like 'remove_config_source' and 'fetch_config' by focusing on adding a 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 context: 'Allows fetching configs from private/team repos' and 'referenced by fetch_config.' Lacks explicit when-not-to-use or alternatives, but the sibling list makes it clear.

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