Replace website PHP options

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

Goes well beyond the destructiveHint annotation by explaining exactly what gets reset: any option not in the request, and all options when an empty array is sent. This is the critical behavioral trait an agent must know before calling.

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?

Three sentences with no filler. The purpose is front-loaded, followed immediately by the most important behavioral warning and the empty-array edge case.

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?

With only two required parameters, full schema coverage, and no output schema, the description covers everything needed to call the tool correctly. The reset semantics and the prerequisite call to the options endpoint make the contract complete.

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 parameter names and constraints are already documented. The description adds important semantics for the options parameter: it must contain the full desired set, and omissions mean reset-to-default.

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?

States a specific verb ('Replaces'), resource ('custom php.ini values on an Agency Plan website'), and the replacement behavior. This cleanly separates it from sibling tools like listing PHP options or replacing PHP extensions.

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?

Gives explicit usage guidance: call the options endpoint first and send the full desired set, since omitted options are reset. It lacks explicit contrasts with sibling tools, but the workflow instruction is concrete and actionable.

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