ise_openapi_deployment_node_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. It states this is a read/list operation (safe) but doesn't disclose pagination behavior, ordering, whether the response includes all node details, or any auth requirements. For a tool with no annotation coverage, the description adds limited behavioral context beyond the basic 'list all nodes' claim.

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 with the endpoint reference. It's appropriately brief and front-loaded with the purpose. No wasted words, though it could add minimal value with pagination notes.

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-type tool with no output schema and no annotations, the description is minimal. It states what it does but does not describe return format, pagination, ordering, or clarify what 'nodes' means in the deployment context. The deployment parameter documentation helps, but overall this is a thin description for a tool that would benefit from more operational context.

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 the deployment parameter has a description; page and size have none). The description itself adds nothing about parameters. The deployment parameter is well documented in the schema with format examples and disambiguation guidance, but page/size semantics and defaults are not explained anywhere - the schema has defaults (1 and 100) but no description. This partially compensates but leaves gaps.

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 the verb+resource: 'Retrieve the list of all the nodes that are deployed in the cluster' with the endpoint (GET /api/v1/deployment/node). It distinguishes 'list' from sibling 'ise_openapi_deployment_node_get' (retrieve single node) and 'node_group_list'. However, the [Deployment] label and endpoint reference are useful; purpose is clear but not exhaustive about the distinction from node_group.

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 this is for listing deployed cluster nodes, and the sibling set includes ise_openapi_deployment_node_get for single-node retrieval and ise_openapi_deployment_node_group_list for groups, giving implicit differentiation. The deployment parameter description also explains when to omit it (use only/default deployment) and directs to ise_list_deployments for choices, providing clear context for usage.

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