ise_ers_list_networkdevice

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

No annotations are provided, so the description carries full burden. It states 'Paginated' but gives no return format, no indication of default behavior beyond page/size, no warning about large result sets, no auth or deployment requirements. For a read/list tool with zero annotation coverage, this is thin.

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 short sentences with no waste. 'List all Network Devices (NADs). Paginated.' is maximally concise for what it conveys.

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 simple list tool with 3 optional params, no required params, and no output schema, the description is adequate but thin. It doesn't mention return shape, default pagination behavior, or rate considerations. With zero annotations, more behavioral context would help. However, it's a straightforward list operation so the gap is moderate.

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% (1 of 3 params documented). The description mentions 'Paginated' which relates to page/size, but the deployment parameter is well-documented in the schema itself. The page and size parameters lack schema descriptions and the tool description doesn't compensate for them.

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 'List all Network Devices (NADs)' with a clear verb+resource. It distinguishes from sibling 'get_networkdevice' (single) and 'search_networkdevice' (search/filter) via the 'List all' phrasing. However, it doesn't explicitly contrast with the sibling search tool.

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 provides no guidance on when to use this tool versus alternatives. Siblings like ise_ers_search_networkdevice presumably handle filtering, but the description doesn't clarify this tool is for unfiltered listing vs. targeted retrieval. It only mentions pagination, not usage context.

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