ise_openapi_radius_policy_set_get

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 states it's a 'GET' operation (read-only), which is useful, but provides no detail about error cases (e.g., invalid/nonexistent policy set ID), authentication requirements, rate limits, or what the returned attributes actually contain. For a read operation, this is a moderate gap but not severe.

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 concise sentence with the endpoint path embedded. It's efficient but very terse—it reads more like an auto-generated stub ('[Policy: Network Access] Network Access - Get policy set attributes') than a thoughtfully written description. It's short enough to be scannable but misses opportunities to add value in that short space.

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 read operation with a simple GET-by-ID pattern, code coverage is 100% on parameters and there's no output schema requirement. The description is adequate for basic usage (fetch a policy set by ID), but given the absence of annotations and the complexity of picking the right RADIUS policy tool among many siblings (list, create, update, delete, get), the description could do more to orient the agent about which policy set type and context is targeted.

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 100%, so the schema already documents both parameters (id as path parameter, deployment as target ISE deployment selector). The description adds essentially nothing beyond the schema for parameters. The deployment parameter has a rich schema description explaining name/slug/number options and pointing to ise_list_deployments. Baseline 3 is appropriate since the schema carries the weight.

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 states '[Policy: Network Access] Network Access - Get policy set attributes' with the HTTP verb 'GET' and target resource 'policy-set/{id}'. It clearly indicates a read operation for a specific policy set by ID. It doesn't explicitly differentiate from sibling tools like ise_openapi_radius_policy_set_list, but the GET-by-ID semantics are reasonably clear from the endpoint path.

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 says 'Get policy set attributes' which implies fetching a specific policy set's details, and the choice of '{id}' in the path implies you need a known ID (which would come from the list call). However, there's no explicit statement about when to use this vs. list/get alternatives, nor any exclusion guidance or context about when this specific API should be preferred.

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