ise_ers_search_networkdevice

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

No annotations are provided, so the description carries full behavioral burden. It does not disclose pagination behavior beyond schema defaults, whether results are returned in a particular format, sorting semantics, or any side effects. For a search/read tool this is somewhat less critical, but the description adds no behavioral context beyond the verb itself.

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 efficient sentence with no wasted words. It's concise and front-loaded with the core purpose. However, given the minimal content, more useful detail could have been added without harming conciseness.

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?

There's no output schema and annotations are absent, so the description should compensate. It fails to explain ERS filter expression syntax, pagination/sort behavior, or how results differ between this and the list variant. For a search/filter tool with undocumented filter semantics, this leaves meaningful gaps for the agent.

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 20%, so the description bears some responsibility for parameter meaning. The filter and sort parameters are underexplained - the description mentions 'ERS filter expressions' but doesn't detail the syntax or provide examples. The deployment parameter is well-described in the schema itself. It's minimally adequate but doesn't enrich filter/sort semantics meaningfully.

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 'Search/filter Network Devices (NADs) with ERS filter expressions' clearly states the verb (search/filter), resource (Network Devices/NADs), and mechanism (ERS filter expressions). It distinguishes from the sibling ise_ers_list_networkdevice (which presumably returns all) and ise_ers_get_networkdevice (single item retrieval), though it doesn't explicitly name those as alternatives.

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 tool is for filtering/searching devices but provides no explicit guidance on when to use it versus ise_ers_search_endpoint, ise_ers_search_networkdevicegroup, or generic ise_ers_search. There's no explanation of when to use this over the list variant, no filter syntax examples, and no exclusions stated.

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