nexterm_shutdown_integration_entry

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

The annotations already disclose destructiveHint=true, openWorldHint=true, idempotentHint=false, and readOnlyHint=false, so the safety profile is covered. The description adds useful context by framing the action as a request for a guest shutdown of an external resource, but it does not explain whether the request is asynchronous, what permissions are needed, or what side effects occur.

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, front-loaded sentence with no wasted words. It communicates the core action and target immediately.

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 destructive external action with a required entry_id and no output schema, the description is missing key context: how entry_id is sourced, how this differs from stop/start siblings, and what the request returns or whether it is asynchronous. The annotations cover the safety hints, but the description does not complete the picture needed for confident invocation.

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%, so the description must carry parameter meaning. It only implies that entry_id identifies an integration entry; it does not clarify where to obtain the ID, whether it refers to the integration entry rather than the external resource, or any additional constraints beyond the schema's integer and minimum fields.

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 action and target: request a guest shutdown for the external resource represented by an integration entry. It is clear what the tool does, but it does not distinguish this from the very similar sibling nexterm_stop_integration_entry, leaving the shutdown-vs-stop distinction unexplained.

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?

There is no explicit when-to-use guidance, no exclusion criteria, and no named alternative. An agent can infer that this is for shutdown, but it cannot tell from the description when to choose this over nexterm_stop_integration_entry or nexterm_start_integration_entry.

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