ise_openapi_deployment_node_group_list

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

No annotations are provided, so the description carries the full burden of behavioral disclosure. It does not disclose that this is a safe read-only operation, what the response structure looks like, pagination behavior beyond the existence of page/size params, or any potential errors. For a list tool with zero annotation coverage, this is a notable gap.

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 concise sentence that communicates the core purpose efficiently with no fluff. The endpoint URL is useful reference. It's appropriately sized for a simple list operation, though the deployment parameter guidance lives in the schema rather than the description.

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 list tool with no output schema and no annotations, the description provides minimal behavioral context but is adequate for a straightforward read operation. The 33% schema coverage means the page/size parameters lack documentation. The tool is relatively simple (list operation, no required params), which lowers complexity, but it could benefit from mentioning pagination or filtering behavior.

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 only 33% — only 'deployment' has a description. That parameter description is genuinely helpful, explaining the accepted formats (name, slug, number) and the default behavior. However, 'page' and 'size' have no description, and the tool description adds nothing about them beyond their existence in the schema. The description partially compensates but doesn't fully cover the gap.

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 'Retrieve the list of all the node groups' uses a clear verb+resource, indicating a list/read operation on node groups within a deployment. The '[Deployment]' prefix and endpoint URL add helpful scoping. It is somewhat distinguishable from siblings like ise_openapi_deployment_node_list, though it doesn't explicitly differentiate between node groups and nodes.

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 description implies a read/list context but provides no when-to-use guidance or exclusions. There are no alternatives named. The parameter description for 'deployment' does add useful selection guidance (omit for default, call ise_list_deployments for choices), which helps with usage, but the tool-level description itself lacks explicit usage context.

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