query_racf_audit

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

The annotations already establish read-only, idempotent, non-destructive, open-world behavior. The description adds source context (configured USS path or dataset) and filter coverage, but it does not disclose return format, authorization requirements, or how errors or missing audit data are handled.

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 two compact sentences with the purpose front-loaded and no wasted wording. The filter list is secondary and supports quick scanning without overwhelming the reader.

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 an eight-parameter read-only query with full schema coverage and rich annotations, the definition is adequate to invoke the tool. Still, with no output schema it does not describe what an audit record contains, and it does not connect the environment parameter to list_environments in prose.

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 parameter semantics are already well documented in the schema. The description names most filter categories, but it adds no syntax or behavioral detail beyond the schema and omits maxResults and environment from the prose.

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 gives a specific verb and resource: query RACF security audit records, and clarifies the source is a configured USS path or dataset. It is clear what the tool does, but it does not explicitly differentiate itself from nearby security/log-analysis siblings such as security_posture_summary or analyze_logrec.

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 states that audit records can be queried and lists supported filters, which implies when the tool is useful. However, it gives no explicit when-to-use/when-not-to-use guidance and does not name alternatives for related security posture or log analysis tasks.

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