ise_ers_search_ancendpoint

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

No annotations are provided, so the description carries full behavioral disclosure burden. It discloses nothing beyond a search/filter operation. It doesn't state pagination behavior, what the response contains, whether typically 'search' returns multiple matches while 'get' returns one, or any ERS API idiosyncrasies. With zero annotations, this is a significant 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?

A single concise sentence with no waste. It's appropriately brief given the tool's simple nature, though it could have used the space budget to add more useful context like filter expression syntax or ERS specifics.

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?

The tool has 5 params, no output schema, no annotations, and 80% of parameters undocumented. For a search tool in a large family of similarly-named siblings, the description should clarify the filter expression syntax, pagination, and behavioral distinction from search_ancpolicy and list_ancendpoint. It's under-specified for the complexity of the ERS API.

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% (5 params, only 'deployment' documented). The description mentions 'ERS filter expressions' but doesn't explain the format of the 'filter' parameter potential syntax. The deployment parameter has a helpful description in the schema itself. The description adds minimal value beyond the schema and doesn't compensate for the low coverage 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 'Search/filter ANC Endpoints with ERS filter expressions' states a clear verb+resource, but it's somewhat terse. It distinguishes from list/get siblings by emphasizing search/filter, but doesn't explain what ANC Endpoints are or what the search returns. The purpose is clear enough but minimal.

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?

No guidance on when to use this tool vs alternatives. There are close siblings like ise_ers_list_ancendpoint, ise_ers_get_ancendpoint, and ise_ers_search_ancpolicy. The description doesn't distinguish when to use search vs list, nor mention the search_ancpolicy sibling. No exclusions or alternative recommendations.

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