ise_dc_view_threat_events

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

With no annotations provided, the description carries the full burden of behavioral disclosure. It identifies this as a read/report tool ('[Report]') but does not state that it is non-destructive, whether it needs specific permissions, pagination behavior beyond the 'limit' parameter, or what happens on empty results. The listing of filterable columns adds some useful context but not behavioral guarantees.

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?

Two sentences, zero wasted words. The first sentence states purpose, the second enumerates usable columns. It is front-loaded with the tool type and resource, then lists the actionable filter surface. Appropriate density for a reporting tool.

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 read-only filtering tool with 100% schema coverage and no output schema, the description is reasonably complete. However, given the large sibling family (many ise_dc_view_* report tools with similar filter semantics), a bit more differentiation of what makes threat events unique would improve completeness. The listing of filterable columns partially compensates for the lack of output schema.

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 are documented in the schema. Yet the description adds value by listing the actual column names (LOGGED_AT, MAC_ADDRESS, etc.) that map to filter_column, which the schema alone doesn't enumerate. The description also mentions the '[Report]' nature and filtering capability, supplementing the schema-level parameter docs.

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 '[Report] Threat Events: Log of threat events received from various sources' with a specific verb (view/report) and explicit resource (threat events log). It lists filterable columns and is clearly distinguished from siblings: it's one of the ise_dc_view_* family but uniquely targets threat events, differentiating from radius/tacacs/endpoint view tools.

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 as a reporting tool ('[Report]', filterable columns) but does not explicitly state when to use this vs alternatives. It names the supported filters which helps contextualize usage, but provides no exclusions or explicit alternative tools. The '[Report]' prefix and the view-tool family context give reasonable implied guidance but not explicit when/when-not direction.

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