get_user_audit_logs

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

With no annotations provided, the description carries the full burden. It indicates a read operation via 'Get' but does not disclose potential permission requirements, pagination, or what 'relevant' logs means. The output schema covers return structure, but behavioral traits like authentication needs are absent. This is a moderate gap for a sensitive resource like audit logs.

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, front-loaded sentence that efficiently conveys the essential purpose and key parameters. No wasted words or redundant information.

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 simple retrieval tool with an output schema present, the description covers the core semantics and parameters. It lacks nuance about permissions or data volume, but these are not critical given the schema and the straightforward nature of the operation. It is complete enough for an agent to select and invoke the tool correctly.

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?

The schema has no descriptions (0% coverage), but the description explains both parameters: user_id as the lookup key and days as the time window with a default of 30. This adds meaning beyond the bare schema property names, though it could be richer (e.g., allowed range for days, format of user_id).

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 the verb 'Get', the resource 'directory audit logs', and the scope 'for a user by user_id' plus time window. This unambiguously distinguishes it from sibling tools like get_user_sign_ins or get_user_mfa_status, which target different data.

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 clear context for use: retrieving audit logs for a specific user within a configurable time range. It does not explicitly mention alternatives or when not to use it, but the specificity of 'audit logs' makes the intended use obvious. No exclusions are stated, but none are needed for such a focused tool.

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