Dig Init

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

Annotations declare idempotentHint=true and destructiveHint=false. Description adds that the tool is only available when no config exists, which clarifies the idempotency constraint—running it multiple times may cause errors. This goes beyond annotations by specifying availability condition and required restart.

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 short sentences with no wasted words. The description is front-loaded with the main action and then provides usage constraints and follow-up steps. Every sentence adds value.

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?

For a tool with no output schema and no parameters, the description covers the init process, availability condition, and required post-step. It does not mention error cases or output (e.g., what file is created), but given the simplicity, it is nearly complete.

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 tool has no parameters, and schema coverage is 100%. Baseline for 0 parameters is 4, and the description appropriately focuses on what the tool does without needing param details.

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?

Description clearly states the tool bootstraps mcp-digger by creating a starter config file. It specifies the action (create) and the resource (starter config file). The sibling tool 'dig_status' likely checks status, so this distinguishes initialization from status checking.

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?

Explicitly states 'Only available when no config exists', setting clear usage condition. Also provides post-run instructions (edit template, restart server). Could mention that dig_status is for checking status but not necessary for a one-time setup tool.

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