okta_search_user_system_logs

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

No annotations are provided, so the description must carry the full burden of behavioral disclosure. It only states 'Search recent System Log events' without explaining what 'recent' means, any rate limits, pagination, or the read-only nature. Minimal behavioral information is added beyond the basic action.

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 sentence, which is concise, but it omits critical information. It is not verbose, but it sacrifices completeness for brevity, making it less useful than a slightly longer but more informative description.

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, no annotations, and incomplete parameter explanations, the description lacks completeness. It does not describe the return format, filtering behavior, or how to use optional parameters. The tool has 6 parameters, and the description only partially addresses one.

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 0%, and the description only mentions the 'user' parameter (login, email, or user ID). It does not explain the purpose or constraints of the other five parameters (limit, since, until, eventType, outcomeResult). The description adds little semantic value beyond what minimal schema information exists.

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 it searches System Log events for a user by login, email, or user ID. It specifies the resource and the filtering criterion, distinguishing it from sibling tool 'okta_list_system_logs' which lists all logs without user filter.

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 when to use this tool (when filtering by user identifier) but does not explicitly state when not to use it or mention alternatives. The presence of a sibling tool for general log listing provides context, but the description lacks explicit usage boundaries.

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