config_password

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

No annotations are provided, so the description carries full burden. It states 'updates' but does not disclose side effects (e.g., overwrites existing secrets), authorization needs, or whether the operation is reversible. Minimal behavioral context beyond the action itself.

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 brief sentence, front-loaded with the core action. It is not verbose, but it could be more informative about usage context or parameter format. Still, it efficiently conveys the primary purpose.

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 the complexity (4 parameters, no output schema, no annotations) and many sibling config tools, the description lacks completeness. It does not explain how this tool differs from config_update for non-password updates, does not provide an example of the parameters JSON, and does not mention if values should be pre-obscured (core_obscure sibling exists).

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 coverage is 100% with clear descriptions for each parameter. The tool description adds little beyond the schema (e.g., 'sets obscured password fields'). The schema already explains that parameters is a JSON object with `pass`. Baseline 3 is appropriate as the description does not significantly enhance parameter meaning.

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 'Update remote secrets — Sets obscured password fields for a remote configuration.' It uses specific verb ('Update') and resource ('remote secrets'), and distinguishes from siblings like config_update (general settings) and core_obscure (obscuring operation).

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?

No guidance on when to use this tool vs alternatives (e.g., config_update). Does not specify prerequisites, such as needing to have the remote configured first, or when not to use it. Implied only by the description's focus on password fields.

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