harness_configure

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

With no annotations, the description carries full behavioral disclosure burden. It mentions 'read or update' implying mutation but provides no details on side effects, idempotency, or safety characteristics. The description does not add behavioral context beyond the basic verb-resource pairing.

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 sentence efficiently conveying the core purpose. It could benefit from slightly more structure but achieves conciseness without unnecessary words.

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 tool updates a configuration file (potential side effects), has nested parameters, and no output schema, the description lacks completeness. It does not explain return values, error cases, or how to properly use the tool beyond a minimal statement.

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 description coverage is 25% (only project_path described). The description mentions 'provider, model, api_key' and 'render preferences' but does not explain the meaning or relationships of these parameters, nor does it cover the design_mcp parameter at all. This is insufficient compensation for the low schema coverage.

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 the tool reads or updates /harness/config.json, specifying it configures the model for universal mode and render preferences. It uses specific verbs and resource, distinguishing it from sibling tools like harness_status or harness_get_spec.

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 provides no guidance on when to use this tool versus alternatives, nor does it mention prerequisites or exclusion criteria. It only states what the tool does without context for appropriate invocation.

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