ise_openapi_tacacs_shell_profiles_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. The description only states it returns a list of shell profiles, but gives no information about pagination behavior (despite page/size params), default limits (size default 100), whether results are filtered, or what fields each profile contains. For a read operation with no annotation support, this is thin.

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 appended. It's efficient and front-loaded with the resource and action. No wasted prose, though it could arguably include more behavioral detail without bloating.

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?

With no output schema and no annotations, the description should explain more. It doesn't describe what a shell profile contains, pagination mechanics, default size behavior, or how this relates to the Device Admin TACACS configuration flow. For a tool with 3 params and no schema coverage on two of them, the description is inadequate for safe, correct use.

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 33% (only 'deployment' is documented in the schema). The description itself does not elaborate on 'page' or 'size' semantics beyond what a reasonable agent might infer, nor does it explain the response format. However, page/size are conventional and the deployment param is well-documented in the schema. The description adds no parameter value beyond the schema.

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 resource (shell profiles) and scope ([Policy: Device Admin] Device Admin), with a clear verb 'Returns list of'. It includes the REST endpoint path, which adds specificity. It distinguishes from siblings like ise_openapi_tacacs_command_sets_list because it explicitly targets shell profiles in the Device Admin policy namespace.

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 gives no guidance on when to use this tool versus alternatives. It does not mention prerequisites (e.g., needing a TACACS deployment), nor does it differentiate from ise_ers_list_tacacsprofile or ise_openapi_tacacs_command_sets_list. The deployment parameter hints 'Target ISE deployment' but doesn't explain the broader selection context.

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