Configure depsonar

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

Annotations already indicate idempotent, non-destructive, and not read-only, which matches the 'view or update' description. The description adds value by specifying the configuration file location (~/.depsonarrc.json) and illustrating both operations. No contradiction with annotations.

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 brief and front-loaded with the primary action. The example usage adds practical clarity without redundancy. Every sentence serves a purpose, making it 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?

With two simple parameters and no output schema, the description provides sufficient context: where config is stored, what actions are possible, and illustrative examples. It doesn't describe the exact output format for 'show', but that is a minor gap given the tool's simplicity and strong annotations.

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 descriptions cover both parameters fully, so the baseline is 3. The description adds value by giving concrete examples ('Show depsonar config' and 'Set projects directory to ~/Code') that clarify how each parameter is used, going beyond the schema's field definitions.

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 states a specific verb and resource: 'View or update configuration.' This clearly distinguishes it from sibling tools like depsonar_scan or depsonar_alerts, which focus on other actions. The examples reinforce the intended scope.

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 clearly implies this is the tool for configuration tasks, with examples showing both viewing and updating. It doesn't explicitly exclude alternatives or mention when not to use it, but the distinct purpose and examples provide clear context, making it easy to choose this tool over siblings.

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