update_php_version

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

There are no annotations, so the description carries the full burden of behavioral disclosure. It says only that PHP version is updated, without indicating side effects, permissions required, reversibility, or impact on running sites. Nothing beyond the bare operation is disclosed.

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 short phrase, which is concise but severely under-specified rather than appropriately structured. There is no front-loaded detail or useful elaboration; it is too sparse to guide an agent.

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 a mutation tool with two required parameters, no annotations, no output schema, and no parameter descriptions, the description is far too incomplete. It omits any information needed to call the tool correctly or understand its effects.

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 0% and there are two required parameters. The description does not explain what 'id' identifies or how 'version' should be formatted or selected. It provides no meaning beyond the parameter names already visible in the schema.

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 states a specific verb and resource ('Update PHP version'), so the basic action is clear. However, it adds no scope or differentiation from siblings like update_php_conf or list_php_runtimes, and it does not clarify what the 'id' refers to. It is essentially the tool name restated.

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 guidance is given about when to use this tool versus alternatives. There is no mention of prerequisites, applicable contexts, or sibling tools such as update_php_conf or install_php_extension.

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