sap_get_user_audit

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

The description indicates the tool is read-only and non-destructive ('read-only user audit'), providing basic safety assurance. However, with no annotations, it does not disclose other behaviors like performance impact or error handling.

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 lacks structure. It is front-loaded with purpose but misses details that would make it more informative.

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?

Given the tool has an output schema, the description should provide context on what the audit data contains. It does not mention return values, pagination, or how the output relates to the input, leaving the agent with minimal context.

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 description adds no meaning to the input schema parameters ('user' and 'destination'). With 0% schema description coverage, the description should compensate but fails to explain what these parameters do or their expected values.

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 combines BAPIs and USR02 reads for a 'read-only user audit', specifying the verb (combines, reads) and resource (user audit). It distinguishes from siblings like sap_audit_tail by focusing on user-specific audit 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?

No guidance on when to use this tool versus alternatives. The description does not mention prerequisites, intended scenarios, or cases where other tools like sap_get_syslog might be more appropriate.

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