ise_openapi_tacacs_policy_set_list

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

No annotations are provided, so the description carries full behavioral disclosure burden. It only states the operation (list) and endpoint but doesn't describe pagination behavior, response format, rate limits, or whether this returns all policy sets across deployments. The 'deployment' parameter behavior is only hinted at via the schema, not explained behaviorally.

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 line stating purpose and endpoint. It's efficient and front-loaded, though it could be slightly more informative without bloat. Minimal waste.

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?

No output schema to compensate for absence of return-value documentation. The tool is a list operation with 3 params but provides no information about what the response contains, how results are paginated, or what filters beyond page/size are available. For a policy set listing tool in a complex domain (TACACS/Device Admin), more detail would help the agent understand what it's retrieving.

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' has a description; 'page' and 'size' lack descriptions). The description itself doesn't add parameter information. However, 'page', 'size', and 'deployment' are fairly self-explanatory given typical list APIs, and the deployment parameter has a solid schema description. Baseline 3 is reasonable but it doesn't compensate for the two undocumented params.

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 'Device Admin - List of policy sets' with the HTTP GET endpoint. It clearly identifies the verb (List) and resource (TACACS policy sets under Device Admin). It distinguishes from siblings like radius_policy_set_list by the 'TACACS' and 'Device Admin' scoping, though it doesn't explicitly contrast with them.

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 the API path but provides no guidance on when to use this vs the radius policy set list or the ERS-based tools. Usage context is implied by the name (TACACS vs RADIUS) but not explicitly stated. No exclusions or alternative recommendations are given.

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