ise_ers_get_ancpolicy

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

With no annotations provided, the description carries full burden for behavioral disclosure. It only states what the tool does (get by ID) without describing any side effects, required permissions, error behaviors, or whether this is a safe read-only operation. For a tool in a security-focused ISE product, the lack of permission/auth context 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 single short sentence with zero wasted words. It is front-loaded and immediately communicates the tool's purpose with no verbosity.

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 simple 'get by ID' resource tool, the description is minimally adequate. The tool is straightforward (2 params, 1 required, no output schema, no nesting), so the bare description covers the core use case. However, given the large sibling family of ERS tools with list/search/get variants, a brief note distinguishing this from list/search alternatives would improve completeness.

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 50% (the id parameter lacks a description). However, the tool name and description clearly indicate 'id' is the ANC policy ID to fetch, which the description adds meaning to. The deployment parameter benefits from a rich schema description. The description meaningfully orients the id parameter toward the ANC policy resource context.

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 'Get a single ANC Policies object by ID' uses a clear verb-resource pattern and specifies the retrieval mechanism (by ID). It clearly distinguishes from sibling get tools targeting other resource types like downloadableacl or guesttype, but doesn't explicitly differentiate from the generic ise_ers_get or sibling ise_ers_get_ancendpoint beyond the resource name.

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 provides no guidance on when to use this tool vs. alternatives. The siblings include ise_ers_list_ancpolicy, ise_ers_search_ancpolicy, and generic ise_ers_get for the same ANC policy resource, but the description doesn't explain when to choose this specific 'get by ID' variant over the search or list alternatives.

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