DescribeByList

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

No annotations provided. Description only notes [read-only], but does not disclose additional behaviors such as output format, pagination, or limits. Minimal transparency beyond the read-only tag.

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 sentences, no wasted words. Front-loaded with read-only and purpose. Highly concise for the information conveyed.

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?

No output schema and description omits return format. For a batch tool, missing information about what 'description' entails (e.g., structure of each object's description). Adequate but not fully 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?

Schema description coverage is 0% per context. Description adds the input structure and lists possible types, providing meaning beyond the bare schema. However, it does not explain parameter constraints or defaults.

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 'Batch description for a list of ABAP objects,' specifying verb and resource. It lists object types, distinguishing it from siblings that target single objects or actions.

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?

Description implies use for batch description but lacks explicit guidance on when to use this tool over alternatives like GetObjectInfo or GetClass. No when-not-to-use or alternative mentions.

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