engine_maxion_deactivateNOT IMPLEMENTED — returns an error. The Maxion engine exposes no deactivate operation, so no governor or power state is changed. Use engine_maxion_status for live telemetry.
| Name | Required | Description | Default |
|---|---|---|---|
No arguments | |||
| Name | Required | Description | Default |
|---|---|---|---|
| content | No | Deactivation status message. |
Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
The description discloses that it returns an error and changes no governor or power state, aligning with the idempotentHint and destructiveHint annotations. It adds implementation status context that annotations don't capture, giving the agent a full picture.
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 front-loaded with the critical 'NOT IMPLEMENTED' notice, then explains consequences and provides an alternative. Every word earns its place—no filler or repetition.
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 stub tool, the description fully covers what an agent needs: it's unimplemented, has no side effects, and points to a useful alternative. The existence of an output schema doesn't require elaboration here, and the description is complete for its simple purpose.
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 zero parameters and full schema coverage, the description has nothing to add. The baseline of 4 is appropriate because the schema already trivially documents the absence of parameters.
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 that the tool is not implemented and returns an error, explicitly distinguishing it from functional siblings like engine_maxion_activate and engine_maxion_status. It identifies the intended operation (deactivate) but immediately signals it's a stub.
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?
It explicitly tells the agent not to use this tool due to non-implementation, and recommends engine_maxion_status for live telemetry. This provides a clear alternative and implicitly warns against relying on this tool.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.
Add one secure layer between your agents and this server.
Each tool has a distinct name and purpose within its domain (billing, engine, media, security, storage, gateway). While there is some semantic overlap (e.g., engine_maxion_status vs. engine_maxion_diagnostics), the specific functions are clear enough to avoid misselection.
Naming patterns are inconsistent: some tools use domain_entity_action (engine_maxion_activate), others use domain_action (billing_activate), and one uses just domain_status (gateway_status). The inclusion of 'lineage0' and '0' suffixes adds further irregularity.
19 tools is on the higher end but justifiable for a multi-service gateway. However, several tools are stubs (NOT IMPLEMENTED), and there are multiple status/diagnostic tools per domain, which makes the set feel padded rather than tightly scoped.
The tool surface is incomplete in several areas: security lacks functional quarantine and logging, engine lacks a working deactivate, and there is no way to manage billing subscriptions or view media history beyond a simple archive list. The presence of explicitly NOT IMPLEMENTED tools highlights these gaps.