Change Site PHP Allocation

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

The annotation 'openWorldHint: true' suggests potential side effects, and the description indicates mutation and async operation via 'operation_id'. However, it lacks details on consequences (e.g., PHP restart, downtime) or prerequisites. It adds some value beyond annotations but is not comprehensive.

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 two concise sentences with no unnecessary words. Action is front-loaded, making it easy for an agent 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?

For a simple parameter-update tool, the description covers basic purpose and return. However, it lacks context on reversibility, prerequisite checks, or operational impact, which is notable given the openWorldHint annotation. Output schema exists, so return values need not be explained, but behavioral context is thin.

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 coverage is 100%, and parameters (site_id, thread_count, thread_memory) are self-explanatory. The description does not add extra meaning, constraints, or units, so baseline score of 3 is appropriate.

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 ('Change PHP worker allocation'), the resource ('for all environments in a site'), and the return value ('Returns an operation_id'). It is specific and distinguishes from siblings like 'kinsta.environments.php-allocation' which likely targets a single environment.

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 (changing PHP allocation across all environments) but does not provide explicit guidance on when to use this vs alternatives, such as per-environment tools. No exclusions or when-not scenarios are mentioned.

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