Report Agent Calls

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

The description mentions general SAP MCP read/write requirements but does not confirm whether this specific tool is a write operation or describe its effects. Annotations indicate readOnlyHint=false, but the description leaves ambiguity.

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 succinct sentences plus a contextual note. No unnecessary words, front-loaded with the core action.

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?

While the output schema may cover returns, the description lacks detail on the tool's effect (e.g., on-chain state change) and has moderate completeness for a write tool.

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?

The single parameter 'callsServed' is fully described in the schema (100% coverage). The description adds no additional meaning beyond the schema, which is baseline adequate.

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 verb 'Report' and resource 'served call count' clearly indicate the tool's purpose. The name and description align, but it does not explicitly distinguish from similar SAP report tools like sap_report_tool_invocations.

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 provides SAP context but lacks criteria for selection among sibling report tools.

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