ise_ers_list_ancpolicy

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

No annotations are provided, so the description carries full burden of behavioral disclosure. It only states 'List all ANC Policies. Paginated.' and doesn't describe what the response looks like, whether results are filtered/sorted, how pagination behaves (total counts, max pages), or side effects. For a read/list operation, the lack of response format or pagination semantics detail is a notable 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 a lean two-sentence construction with zero wasted words. It's front-loaded with the core purpose. However, it's arguably under-specified rather than elegantly concise, but for a simple list operation the brevity is still acceptable.

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 simple paginated list tool with 3 optional parameters and no output schema. The description covers the essence ('List all ANC Policies', paginated). Given its simplicity and self-explanatory params, the description is reasonably complete, though it could mention what fields/resource shape ANC policies return and whether filtering is supported beyond pagination.

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 33%, meaning only the deployment parameter is documented in the schema. The description adds no parameter details; page and size are unnamed in the description. However, page/size are self-explanatory for a paginated list and deployment is well-documented in schema, so the description adds marginal value but doesn't severely hinder parameter understanding given the simplicity.

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 'List all ANC Policies. Paginated.' uses a clear verb+resource ('List ANC Policies') and notes pagination. It distinguishes from get/search variants among siblings (ise_ers_get_ancpolicy, ise_ers_search_ancpolicy) through the 'List' verb, though it doesn't explicitly contrast them. Slightly terse but unambiguous.

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 a list operation but provides no explicit when-to-use guidance or exclusions versus get/search siblings. Among siblings, ise_ers_get_ancpolicy and ise_ers_search_ancpolicy exist but no guidance differentiates when to use list vs get vs search. The deployment parameter schema hints at target selection but description doesn't elaborate usage context.

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