ise_dc_view_tacacs_authorization

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 labels the tool as a 'Report' (implying read-only safety) but never explicitly states it performs a safe read, doesn't describe return format, pagination behavior beyond the limit parameter, or time-filtering semantics of days_back. For a report/data-viewing tool with zero annotation coverage, key behavioral context is missing.

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, efficient sentence that front-loads the purpose and then enumerates the columns. It's compact with no filler or repetition. Slight room for improvement in that it could add one more clause about usage decisions, but the current structure is clean and wastes no 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?

The tool has 7 parameters, no output schema, and no annotations. The description is adequate for a filtered report-viewing tool: it names the columns, implies filtering, and the schema documents all params. However, it doesn't mention what the returned data looks like (since there's no output schema), pagination defaults, or how days_back interacts with time columns. For a report tool, this is acceptable but not fully self-sufficient.

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 all 7 parameters already have descriptions in the schema. The description adds meaningful context by enumerating the filterable columns (which map conceptually to filter_column and order_by choices), providing value beyond the raw schema. The parameters themselves (limit, order_by, days_back, filter_op, deployment, filter_value, filter_column) are self-explanatory and well-documented in 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 clearly labels this as a [Report] for TACACS Authorization records and explicitly lists all filterable columns (ID, GENERATED_TIME, LOGGED_TIME, ISE_NODE, ATTRIBUTES, EXECUTION_STEPS, STATUS, EVENT). The verb 'provides details of' plus the resource and column scope makes the purpose specific and distinct from sibling report tools like tacacs_authentication and tacacs_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 implies usage for reading TACACS authorization records but provides no when-to-use guidance or exclusions versus alternatives. There are related sibling tools (ise_dc_view_tacacs_authentication, ise_dc_view_tacacs_accounting, ise_openapi_tacacs_authorization_list) that could be confused, but the description doesn't clarify when to pick this one over them. The 'Report' prefix hints at read-only reporting, but no explicit guidance is given.

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