GetObjectsByType

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

Only adds '[read-only]' for behavioral info. No annotations provided, so description carries full burden but fails to disclose other traits like prerequisites, rate limits, or error 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?

Two concise sentences with no wasted words; front-loaded with read-only tag. Could be more structured (e.g., bullet points for parameters) but efficient for the information given.

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?

With 6 parameters and no output schema, description lacks details on output format, pagination, or parameter constraints. Not complete for an AI agent to confidently invoke without additional 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?

Tool description does not explain parameter meanings beyond what the schema provides. Schema descriptions are minimal ('[read-only]' tags) and don't add value, leaving parameters like parent_name and parent_type ambiguous.

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?

Description clearly states it retrieves ABAP objects of a specific type under a parent node, with examples. It differentiates from siblings like GetObjectsList by focusing on type filtering, but could be more precise about the parent node context.

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?

Provides use case guidance ('useful for listing all objects of one type within a package or composite object') but lacks explicit when-not or alternatives among the many sibling Get tools.

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