combell_linux_hostings_set_php_apcu

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

Annotations already indicate this is non-read-only, idempotent, and non-destructive. The description adds the operation semantics (enable/disable and set size), but does not disclose additional behavioral details such as prerequisites, effects on existing cache state, or what happens when apcu_size is omitted.

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?

A single, well-structured sentence that front-loads the core action and includes the size unit. No redundant or filler content.

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 setter with flat parameters and no output schema, the description plus schema is largely sufficient. It lacks explicit guidance on parameter interplay (e.g., whether apcu_size is only relevant when enabled), but this is a minor gap given the tool's low complexity.

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?

With only 33% schema coverage, the description compensates by clarifying the 'enabled' parameter through 'Enable or disable' and the 'apcu_size' parameter through 'set its size (in MB)'. The 'domain_name' parameter is not explicitly described, but its role is strongly implied by the resource context.

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 ('Enable or disable'), a specific resource ('PHP APCu caching on a Linux hosting'), and the size-setting capability. This clearly differentiates it from sibling tools like set_php_version or set_gzip.

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 usage context is implied: use this when you need to manage APCu caching for a Linux hosting. However, the description does not explicitly mention alternatives or state when not to use this tool, relying on the tool name and general semantics.

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