set_php_ini_directives

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

No annotations are provided, so the description carries the full burden. 'Set' implies mutation, but the description does not disclose whether the provided content replaces the entire INI file, merges with existing directives, or requires specific permissions. It also doesn't mention reversibility or potential side effects on unrelated directives, leaving significant behavioral ambiguity.

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, front-loaded sentence with two concrete examples. Every word earns its place; there is no filler or redundancy.

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?

This is a mutation tool with no annotations and no output schema. While the parameter is well-documented, the description omits critical behavioral context: does it overwrite all directives or only update the given ones? Without clarifying the effect on existing configuration, the description is not complete enough for safe usage, especially for a tool that modifies server settings.

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 100%, with the parameter 'content' already described as 'PHP INI content (e.g., ...)'. The description only repeats similar examples without adding deeper semantic meaning, such as whether the content is merged or replaces existing settings. Baseline 3 is appropriate since the schema does the heavy lifting.

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 uses a specific verb ('Set') and resource ('PHP INI directives') with concrete examples (memory_limit, upload_max_filesize). It clearly distinguishes from the sibling tool 'get_php_ini_directives' which retrieves directives, making the operation unambiguous.

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 implies usage: you use it to set PHP INI directives. However, it does not explicitly mention when not to use it or point to alternatives like 'get_php_ini_directives' for reading current values. There is no exclusion guidance, only implied context.

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