da_config_local

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

With no annotations, the description carries the full burden of behavioral disclosure, and it only states a noun phrase. It does not state whether the operation is read-only, whether it returns a merged view, or whether it has side effects, leaving behavior entirely opaque.

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 short and has no wasted words, but it is under-specified rather than concise. A single noun phrase does not earn its place because it does not communicate the tool's action or behavior.

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 no parameters and an output schema, the description is incomplete because it does not state what the tool does. The missing operation is fundamental enough that an agent cannot reliably decide to invoke this tool over da_config_active, da_config_default, or da_config_local_update.

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 input schema is empty with zero parameters, so there are no parameter semantics for the description to document. The baseline of 4 applies because the description does not need to compensate for any parameter coverage gap.

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 identifies a specific resource—local overrides in directadmin.conf—but lacks any verb, so it is not clear whether this tool reads, applies, or validates those overrides. It hints at the 'local' distinction from da_config_active and da_config_default, but does not explicitly differentiate among the config-related siblings.

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 when-to-use guidance is provided, and no alternatives or exclusions are mentioned. An agent must infer from the tool name and sibling cluster that this is likely the reader for local overrides, which is not enough guidance.

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