ise_ers_list_sgt

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 mentions pagination but provides no detail about what this means concretely — how results are ordered, what the return shape is, whether there are limits, or what happens with large result sets. For a read/list operation with zero annotation coverage, more behavioral context would be expected.

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 extremely concise — a single short sentence stating purpose and pagination. It's front-loaded and has zero superfluous text. It is appropriately sized given that most parameter detail is in the schema.

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 paginated list operation shared across many sibling list_ tools, the description is adequate for basic use. However, there is no output schema, no annotation coverage, and the description doesn't clarify the pagination contract (return format, total counts, page limits). It's minimally viable but relies on the agent understanding the broader ISE ERS list pattern.

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; 'page' and 'size' rely on their names and defaults). The description mentions pagination but doesn't explain the page/size semantics beyond what the schema already documents via defaults. The deployment parameter is well-documented in the schema itself. The description adds minimal value beyond the schema for parameters.

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 ('List') and resource ('Security Group Tags'), and mentions it is paginated. It distinguishes itself from sibling tools like ise_ers_get_sgt and ise_ers_search_sgt (which are single-item fetch and search operations, respectively), though it doesn't explicitly reference them. The name ise_ers_list_sgt aligns with many other list_ siblings, making its purpose clear.

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. There are dozens of sibling list_ tools and generic ise_ers_list, but no indication of when to prefer this SGT-specific paginated list over the generic bulk list or search tools. No exclusions or alternative recommendations are given.

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