da_config_default

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

No annotations are provided, so the description carries the full burden of behavioral disclosure. It implies that default directadmin.conf values are somehow exposed, but it does not state whether this is a read-only lookup, what format is returned, or whether any state is affected.

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 very brief with no wasted words, but it is a fragment rather than a complete, self-contained instruction. It is concise in length but lacks a verb, making the structure less helpful than it could be.

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 zero-parameter tool with an output schema, the description does not need to be long. However, it still fails to state the action and does not differentiate this endpoint from closely related config tools, leaving an agent without enough context to select it confidently.

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 zero parameters and the input schema properties object is empty, so there is no parameter semantics burden. The baseline of 4 applies because there are simply no parameters for the description to clarify.

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 'Default directadmin.conf values.' is a noun phrase that essentially restates the tool name da_config_default. It identifies the resource (directadmin.conf default values) but never states the operation, so an agent cannot tell whether this tool returns, lists, applies, or validates those values.

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?

There is no guidance about when to use this tool versus its siblings such as da_config_active, da_config_local, or da_config_local_update. The description gives an agent no criteria for choosing this endpoint over the other config-related tools.

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