Read SAP Runtime Feed

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

Annotations already declare the tool read-only, idempotent and non-destructive, so the description does not need to restate that. 'Bounded... page' adds a small behavioral hint about pagination, but the description does not disclose feed edge semantics, ordering, or how from/to may partition pages.

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 one compact sentence with no filler and front-loads the core action. It earns its place by clarifying both the page semantics and the feed topics, even though parameter-level detail is absent.

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?

For a 7-parameter tool with zero schema descriptions and an output schema, the description is under-specified. It does not explain the pagination contract, what the returned feed records represent, or how required fields like systemId interact with feed categories.

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%, so the description carries the full burden, but it only paraphrases the kind enum values and does not explain systemId, from, to, user, limit, or startIndex. An agent would still need to guess the meaning of the feed cursor and pagination parameters.

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 states a clear verb ('Read') and a specific resource ('bounded ADT feed page'), and explicitly enumerates the four feed categories that map directly to the kind enum. This distinguishes it from sibling runtime tools such as dump/trace read tools, whose object differs.

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 gives no guidance on when to use this tool over alternatives, nor does it name any sibling tool or exclusion condition. It only implies use through the feed categories; for 7-parameter tool with many similar runtime siblings, that is too little.

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