ise_ers_search_networkdevicegroup

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 'ERS filter expressions' but never explains what ERS is, what the filter expression syntax looks like, whether results are paginated, whether it's read-only, or what happens with invalid filters. For a search operation with no annotations, this is a significant transparency 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 appropriately brief at one sentence. It's front-loaded with the primary purpose. No wasted words, but could arguably include slightly more useful behavioral or filter-syntax context without becoming bloated.

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 search tool with 5 parameters, no output schema, and no annotations, the description is thin. It doesn't explain filter expression syntax, pagination behavior, sort format, or what the returned data looks like. With schema coverage at 20%, the description should compensate more for the undocumented filter, page, size, and sort parameters.

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 20% (only the deployment parameter has a description). The description mentions 'filter expressions' but doesn't elaborate on the filter parameter's syntax or accepted format, leaving the most important parameter (filter) unexplained since the schema also lacks description for it. The deployment parameter is well-documented in the schema, offsetting some of 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 states it searches/filters Network Device Groups with ERS filter expressions. The verb+resource is clear, but it doesn't differentiate from the many sibling search tools (ise_ers_search_networkdevice, ise_ers_search_endpointgroup, etc.) beyond the resource type which is already in the name. The 'ERS filter expressions' detail adds some technical specificity.

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 usage for filtering/searching but provides no explicit guidance on when to use this vs alternatives like ise_ers_list_networkdevicegroup (list) or ise_ers_get_networkdevicegroup (get by ID). No exclusions or prerequisites are stated. The deployment parameter hint (call ise_list_deployments) is the only usage guidance present.

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