GetWhereUsed

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

The description includes a read-only hint but lacks additional behavioral details such as permissions, rate limits, or potential side effects. Since no annotations are provided, the description could be more transparent about the tool's behavior.

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 brief and front-loads the read-only nature. Every sentence adds value, and the structure is efficient.

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 lack of an output schema, the description adequately explains the return value ('referencing objects with types and packages'). The tool's complexity is moderate, and the description covers essential aspects.

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 input schema has 100% coverage with clear descriptions. The description adds extra context for the 'enable_all_types' parameter, explaining its effect. Overall, the parameter semantics are well-addressed beyond the schema.

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's function: finding where-used references for ABAP objects. It answers specific user queries and lists supported object types, making it distinct from sibling tools like GetClass or SearchObject.

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 context on when to use (e.g., 'where is X used') but does not explicitly exclude other tools or mention alternatives. The guidance is implied rather than explicit, leaving some ambiguity.

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