SAP Chat Read Latest

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

The description says 'Read' implying read-only, but the annotation readOnlyHint=false indicates the opposite, creating a contradiction. No disclosure of authentication requirements, rate limits, or side effects. The description fails to clarify the behavioral trait beyond the conflicting annotation.

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 a single sentence of 10 words, highly concise with no fluff. Every word contributes to the purpose.

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?

Despite the presence of an output schema, the description lacks context about the ring buffer behavior, when messages are available, or how to use the 5 parameters effectively. The annotation contradiction further reduces completeness.

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 100%, so the schema already documents all parameters. The description adds no additional meaning or context for parameters like topic, roomId, roomKind, etc. Baseline score of 3 is appropriate.

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 verb 'Read', the resource 'latest SAP chat messages', and the source 'room ring buffer'. This distinguishes it from sibling tools like sap_chat_read_all and sap_chat_send_message.

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?

No explicit guidance on when to use this tool versus alternatives. The description mentions 'latest' but does not explain the ring buffer characteristics or when to prefer this over sap_chat_read_all. No scenarios or exclusions provided.

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