ise_dc_view_tacacs_accounting

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

No annotations are provided, so the description carries full burden. It discloses it contains accounting record details and which columns are filterable, but doesn't mention what columns are returned by default (only which are filterable), whether results are paginated, what the time window behavior is, or whether it's a read-only snapshot. The days_back parameter suggests time-based filtering but the description doesn't clarify the view's default time scope.

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 compact—two sentences. The first establishes purpose, the second enumerates the filterable columns. No wasted words. It's front-loaded with the primary action. Slightly useful addition would be elaboration on the days_back default, but it's appropriately sized for a report view.

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 report view with 100% schema coverage, no nested objects, and standard query parameters, the description provides the necessary column list and record type. The list of filterable columns is the main value-add. However, it could be more complete by clarifying the differences among the multiple tacacs_* views (authentication, authorization, accounting, command_accounting) given the breadth of sibling tools.

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 100%, so parameters (limit, order_by, days_back, filter_op, deployment, filter_value, filter_column) are all documented in the schema. The description adds the list of filterable columns (REMOTE_ADDRESS, ID, USERNAME, IDENTITY_GROUP, GENERATED_TIME, LOGGED_TIME, ISE_NODE, AUTHENTICATION_SERVICE), which is genuinely useful beyond the schema since it tells the agent which columns are valid for filter_column. However, it doesn't add depth beyond that list, hitting the baseline 3.

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 this is a view of TACACS accounting records and lists the filterable columns. However, it's titled as a '[Report]' which is generic, and while it distinguishes it among the dc_view siblings by specifying TACACS accounting, it doesn't articulate what makes it different from the related tacacs_authentication and tacacs_authorization views (beyond 'accounting').

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 ise_dc_view_tacacs_authentication or ise_dc_view_tacacs_command_accounting. It doesn't mention when a report view is preferred over ise_dc_query or ise_dc_view. No exclusions or alternatives are given, so an agent must infer appropriateness from the name alone.

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