GetInactiveObjects

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

The description labels the tool as [read-only], indicating it does not modify data. With no annotations provided, this is helpful but lacks further behavioral details such as performance, return size, or authentication requirements.

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 sentences long, front-loaded with the read-only hint and a clear purpose, with no extraneous information. It is optimally concise.

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 simple task with no parameters and no output schema, the description sufficiently covers what the tool does. It could mention the output format or limitations, but for a straightforward list tool, it is largely complete.

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?

There are no parameters in the input schema, so the description has no need to elaborate on parameters. It adequately explains the tool's function 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 retrieves a list of inactive ABAP objects that are modified but not activated. It specifies the types of objects included (classes, tables, CDS views, etc.), making its purpose unambiguous and distinct from sibling tools.

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 implies the tool should be used when needing to see pending activations, but it does not explicitly compare with alternatives like ActivateObjects or other Get* tools, nor does it mention 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.