ise_ers_list_node

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

No annotations are provided, so the description carries full behavioral disclosure burden. The description only mentions 'Paginated' but does not disclose what the response looks like, whether it returns all fields for every node, what the default page size behavior implies, or whether this is a read-only operation. For a list tool with zero annotation coverage, this is a minimal disclosure.

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?

Two efficient sentences with no wasted words. The description is front-loaded with the primary purpose followed by the pagination note. It is appropriately sized for a simple list tool.

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 3 optional parameters and no output schema, the description is adequate but could be richer. The deployment parameter logic is well-documented in the schema itself, and pagination is noted. However, given the complexity of the ISE deployment concept (name/slug/number forms), the description relies heavily on the schema for deployment meaning, and there's no disclosure of result shape or potential large datasets beyond 'Paginated'.

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 coverage is only 33% (only the deployment parameter has a description). The deployment parameter has rich semantics in the schema itself. However, 'page' and 'size' parameters have no description beyond their defaults, and the description text does not add meaning to them beyond 'Paginated' in the description. Given that schema covers deployment well but only 1 of 3 params, the description adds minimal compensation beyond the schema.

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 tool 'List all ISE Nodes' with the verb 'List' and resource 'ISE Nodes'. It distinguishes from sibling list tools by the specific resource (node vs endpoint, downloadableacl, etc.), though it doesn't explicitly contrast with ise_ers_get_node or ise_ers_search_node.

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 mentions 'Paginated' which implies usage context for large result sets. The deployment parameter description provides usage guidance about the target deployment and how to discover choices via ise_list_deployments. However, no explicit guidance on when to use this vs get_node or search_node is given.

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