Get SAP User Detail

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

Annotations already establish read-only, idempotent, non-destructive behavior. The description adds useful behavioral detail beyond that: it names the BAPI, documents the JSON response shape, and indicates optional fields. No contradictions with annotations are present.

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 well-structured with clear Args, Returns, and Examples sections. It is compact, front-loads the core purpose, and every section contributes to correct tool usage.

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 read tool, the description sufficiently covers purpose, parameters, return format, and example usage. It doesn't detail error behavior or authentication requirements, but the annotations and schema already cover the safety profile and parameter constraints, so the missing pieces are minor.

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 coverage is 100%, so both parameters are already described in the schema. The description adds value by giving example usernames and mapping natural-language questions to the username parameter, which helps an agent infer correct invocation from user requests.

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 tool reads SAP user details and names the specific attributes it returns (address, logon data, lock status, roles, profiles). It also identifies the underlying BAPI, which differentiates it from the many read/search tools among the siblings.

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 gives concrete natural-language examples showing when to call it ('What roles does user JSMITH have?', 'Is user VENNELAKA locked?'). It provides clear context for its intended use, though it doesn't explicitly contrast it with alternative sibling tools or state when not to use it.

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