cpanel_uapi_call

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

No annotations are provided, so the description carries the full burden. It only says 'Call any cPanel UAPI module/function directly' without disclosing that some UAPI functions may be destructive, require specific permissions, or have side effects. It also does not describe the response format or error behavior, leaving the agent with no awareness of potential risks or outcomes.

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 sentences, front-loaded with the core action ('Call any cPanel UAPI module/function directly'), and every sentence serves a purpose: what it does, when to use it, and where to find details. There is no unnecessary information.

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?

The tool is a generic catch-all with no output schema and no annotations. The description covers what, why, and how to get more info, but it lacks any mention of behavioral risks, authorization requirements, or expected return structure. For a tool that can invoke arbitrary UAPI functions, this is a notable gap, though the external documentation pointer mitigates some incompleteness.

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?

The input schema provides descriptions for all three parameters (module, function, params) with examples for module. The description adds value by directing the agent to refer to cPanel UAPI documentation for actual names and parameter values, which is essential because the schema only gives generic placeholders. This external reference compensates for the lack of context and enriches parameter understanding.

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 it calls any cPanel UAPI module/function directly, using the specific verb 'Call' and resource 'cPanel UAPI module/function'. It explicitly distinguishes itself from siblings by saying 'Use this for functionality not covered by the other tools,' making its role as a fallback unambiguous.

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?

Provides an explicit when-to-use condition: 'Use this for functionality not covered by the other tools.' This also implicitly tells the agent not to use it for operations already covered by sibling tools. Additionally, it directs the agent to consult cPanel UAPI documentation for names and parameters, which is helpful for correct invocation.

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