ise_dc_view_radius_accounting

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 is purely declarative about what's returned ('details of all the radius accounting records') and lists columns, but does not disclose the security/read-only nature, any quirks about record volume, deduplication, pagination, or how this differs from the '_week' variant. For a report tool with no annotations, 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 efficient sentence, front-loaded with the [Report] classification and the resource name. The column list is dense but useful. No wasted words, though it could be more compact.

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 carries a heavier burden, but it does list the filterable columns and functions as a view/report tool with rich schema param descriptions. The main gap is the absence of any return-format or row-scope detail (e.g., whether all records or a bounded window), which is significant for a 'details of all' report. Decent but not complete.

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 tool description adds the list of filterable columns (TIMESTAMP, VN, AUTHORIZATION_POLICY, FAILURE_REASON, etc.), which is genuinely useful for choosing filter_column values—this supplements the schema. However, this is baseline credit for high coverage; the description mostly repeats import already carried by 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 opens with '[Report] RADIUS Accounting' and states it provides details of all the radius accounting records, listing filterable columns. This clearly indicates a view/report tool returning accounting records. It doesn't explicitly distinguish from ise_dc_view_radius_accounting_week or radius_authentications siblings, but the resource ('radius accounting') and the [Report] tag are specific enough.

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 this is a report/query tool but provides no explicit when-to-use guidance or exclusions vs. alternatives. It doesn't mention the related ise_dc_view_radius_accounting_week (which would be the natural comparison), nor when one should prefer this over the authentications or tacacs accounting tools. The [Report] tag gives mild context but no actionable guidance.

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