ise_ers_search_node

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. The description only states 'Search/filter ISE Nodes with ERS filter expressions' with no mention of pagination behavior, result format, rate limits, error conditions, or whether this is a safe read operation. For a search tool 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 one concise sentence that communicates the core purpose efficiently. However, given the low schema coverage and absence of annotations, there is room for a bit more detail without becoming verbose. The brevity is appropriate for the search/filter family of tools, though slightly under-informative given the documentation gaps elsewhere.

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?

This is a search tool with 5 parameters, 0 required, very low schema coverage, no output schema, and no annotations. The description explains what the tool does but does not compensate for the 'filter' parameter being undocumented (the core ERS filter expression syntax is unhelpful), nor does it clarify return structure or the relationship to sibling search tools. For a tool with this many documentation gaps, the description is insufficiently complete.

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 very low at 20%, with only the 'deployment' parameter carrying a meaningful description. The 'filter' parameter is the core of the search function but has no explanation of the ERS filter expression syntax or format. The description title mentions 'ERS filter expressions' which gives some context, but the filter parameter semantics are left entirely to the agent's inference. The search-related parameters (page, size, sort, filter) are conventional and the deployment parameter is well-documented, partially compensating.

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 ISE Nodes with ERS filter expressions' uses clear verb+resource language identifying it as a search/filter operation on ISE Nodes. It does not explicitly distinguish from siblings like ise_ers_list_node or ise_ers_get_node, but the 'search/filter' language clearly positions it as the filtering variant within the Node family, and the generic ise_ers_search is also present. It clearly states the resource (ISE Nodes) and operation (search/filter), though it lacks explicit sibling differentiation.

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 searching/filtering ISE nodes but provides no explicit when-to-use guidance or alternatives. The pattern among siblings (list/get/search) is conventional and easy to infer, but no exclusions or alternative pointers are given. The deployment parameter hints at calling ise_list_deployments, giving minor context, but no clear guidance on when to prefer this over generic ise_ers_search or list_node.

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