ise_openapi_radius_authentication_list

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. It's a list/read operation but the description doesn't state this explicitly, doesn't note pagination, response format, ordering, or whether the {id} refers to a policy-set that must exist first. For an unannotated tool, 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?

At roughly two clauses, the description is appropriately brief and the core action ('Get authentication rules') is front-loaded. The endpoint path provides useful technical reference without bloat. No wasted words.

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 list operation for a policy-scoped resource with no output schema and no annotations. Given the complexity (nested under policy-set id, RADIUS vs TACACS variants, many sibling list tools), the description should provide more: what the response contains, how it relates to the policy-set, and how it differs from sibling list tools. The description is minimal for the context it operates within.

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%, so the schema already documents both parameters. The description adds little beyond the schema: the explanatory context around the deployment parameter (naming options and fallback to default) is embedded in the schema itself. Baseline 3 is appropriate since schema does the heavy lifting and description adds marginal value.

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 'Get authentication rules' with the endpoint path, providing a specific verb+resource. However, it's mostly just restating the function name/generic context ('authentication list' → 'get authentication rules'), and doesn't articulate scope (all rules in a policy set? filtered?) beyond the path parameter. The 'Network Access' policy classification helps establish domain context.

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 vs. the many sibling radius/tacacs list tools. It doesn't distinguish from ise_openapi_radius_authentication_create, the tacacs_authentication_list sibling, or the generic ise_openapi_request. The description provides no when-to-use or when-not-to-use direction.

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