Change PHP Allocation

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

With only 'openWorldHint: true' annotation, the description carries the full burden. It indicates a mutation ('Change') and mentions an asynchronous return ('operation_id'), but lacks details on side effects, immediacy, or authorization needs.

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 concise with one sentence and no extraneous information. However, it could incorporate more useful details without sacrificing brevity.

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's mutation nature and 'openWorldHint', the description lacks context about impact, best practices, or when changes take effect. The presence of an output schema doesn't compensate for these gaps.

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%, so the baseline is 3. The description adds no extra meaning beyond the schema; for example, it doesn't explain typical values or constraints for 'thread_count' or 'thread_memory'.

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'), the resource ('PHP worker allocation'), and the scope ('for a specific environment'). It distinguishes the tool from siblings like 'php-allocation-site' by implying environment-level operation.

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 exclusions. It only states what the tool does, leaving the agent without context for decision-making.

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