GetObjectsByType

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

Starts with '[read-only]' disclosing the operation's safe nature. No annotations present, so the description carries the full burden. It does not cover other behaviors like error handling, performance, or data completeness.

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: first defines purpose, second gives use case. No redundant information, front-loads the [read-only] flag.

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?

Lacks explanation of output format (despite 'format' parameter), no mention of return structure, and does not clarify how the required parameters interact. With 6 parameters and no output schema, the description is incomplete.

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?

Input schema has 100% parameter description coverage, but each description is minimal (e.g., '[read-only] Parent object name'). The tool description does not add meaning to parameters beyond what the schema provides, so baseline of 3 applies.

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?

Clearly states it retrieves ABAP objects of a specific type under a parent node, with examples (classes, tables, etc.) and use case (listing within a package). Differentiates from siblings like GetObjectInfo (single object) by explicitly mentioning 'all objects of a specific type'.

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 a clear use case: 'listing all objects of one type within a package or composite object.' Does not explicitly state when not to use or name alternatives, but the context is sufficient.

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