ise_openapi_radius_authorization_list

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

No annotations are provided, so the description carries full burden for behavioral disclosure. It fails to disclose that this is a read operation, whether it returns all authorization rules, pagination behavior, or required context (the policy set must already exist). It only echoes the endpoint URL rather than describing behavior.

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 concise at one sentence, with the endpoint embedded for reference. It doesn't repeat schema information. However, it could be restructured to front-load the verb (GET) and resource more clearly rather than the '[Policy: Network Access]' prefix.

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 tool requiring a policy set id and with no output schema, the description doesn't explain what the response contains, whether additional fields like rule count are returned, or how many results to expect. The dependence on first retrieving a policy set id is not mentioned. Given the parameter complexity is low but the API context is specific, this feels incomplete.

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 coverage is 100%, and the deployment parameter has detailed documentation including examples (name, slug, or number formats). However, the description itself adds no parameter context. Since schema coverage is high, baseline 3 is appropriate, though the description doesn't enrich the id parameter's meaning (it's only called the 'path parameter').

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 the API endpoint and '[Policy: Network Access] Network Access - Get authorization rules' clearly identifying it retrieves authorization rules for a policy set. However, it doesn't clearly state this is specifically RADIUS authorization (vs TACACS which has a sibling tool ise_openapi_tacacs_authorization_list) beyond the tool name, and it doesn't indicate whether it lists all rules or rules for a specific set, though the {id} path parameter implies a specific policy set.

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 versus alternatives. It doesn't mention that it requires a policy set id (which must first be obtained from a policy-set listing tool), nor does it distinguish this from the sibling ise_openapi_radius_authorization_create or ise_openapi_tacacs_authorization_list. No exclusions or alternatives are given.

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