set_setup_value

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

With no annotations provided, the description carries the full burden of behavioral disclosure. The warning about caution is generic and does not explain potential side effects, required permissions, persistence behavior, or whether changes take immediate effect. For a tool that modifies global configuration, this is insufficient.

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, direct sentence followed by a concise warning. It is appropriately sized, with no unnecessary wording or repetition, making it easy to parse quickly.

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?

The tool is a generic setter for global configuration constants, which can have widespread effects. However, the description lacks essential context such as when to use it, what cautions to observe, and what the broader impact is. Even with a complete schema, the missing usage and behavioral context makes it incomplete for an agent to safely invoke.

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 schema covers both parameters with clear descriptions (e.g., constant name examples), so baseline is 3. The description adds no additional parameter semantics beyond the schema, but it also doesn't need to since coverage is complete.

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 action: 'Modifier une constante de configuration globale de Dolibarr' (modify a global configuration constant). This distinguishes it from sibling tools that handle specific configuration areas (e.g., configure_vat_mode, configure_fiscal_year) by indicating it is the generic setter for any configuration constant.

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 explicit guidance is given on when to use this tool versus the many sibling configuration tools. It lacks any mention of exclusions, prerequisites, or scenarios where this generic setter is preferred over dedicated configuration tools. The warning 'Utiliser avec précaution' hints at caution but does not provide actionable usage context.

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