ise_ers_list_tacacsprofile

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

With no annotations provided, the description carries full behavioral burden. It notes the tool is 'Paginated' which is useful, but doesn't disclose whether it's a read-only safe operation, whether results are sorted, what the response format is, or whether all profiles are returned or just the first page. It's a list operation so destructive intent is implied absent, but the description doesn't articulate any behavioral nuance beyond pagination.

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 very short (two sentences). While concise, the 'Paginated' note is thin and the description is arguably under-specified rather than efficiently concise. It front-loads the purpose well but provides no additional structured guidance.

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 relatively simple list tool with 3 parameters, no output schema, and no annotations. Given the low complexity, a minimal description might be acceptable, but the lack of usage guidance relative to the many sibling TACACS/ERS tools, plus the pagination nuance, makes it slightly under-complete. It's adequate for a trivial list operation but leaves the agent to guess about response shape and when to use alternatives.

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%, so the description should compensate for the two undocumented params (page, size). The description's 'Paginated' hint partially explains page and size semantics, but it doesn't clarify defaults, maximum size limits, or how results are ordered. The deployment parameter already has a rich description in the schema. The description adds marginal context about pagination but doesn't fully compensate for the 67% coverage gap.

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 clearly states the tool lists all TACACS+ Profiles, using a specific resource ('List all TACACS+ Profiles'). It distinguishes itself from siblings like ise_ers_get_tacacsprofile (single get) and ise_ers_search_tacacsprofile (search) through the 'List all' phrasing, though it doesn't explicitly name those alternatives.

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 like search_tacacsprofile or get_tacacsprofile. It does not mention when a different resource type (e.g., commandsets vs profiles) would be more appropriate, nor does it explain pagination behavior or when the deployment parameter is needed.

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