BatchAnswers

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

With no annotations, the description carries the burden and does reasonably well: it declares read-only, discloses that answers are materialized on first read and cached for later reads, that numbers are processed in parallel, and that unknown numbers yield 'unknown' rather than an error. It does not describe what an 'answer' object contains or whether reads are idempotent across batch restarts.

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?

Front-loaded with the read-only tag and the core action, then the caching and parallelism facts. It is dense semicolon-chained prose, but every clause contributes information about behavior.

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 exists, so the description must convey the return shape, and 'the tool's answer, built from the call's parts of SAP's response' is suggestive but not concrete about the answer's structure or failure representation. The relationship to the batch lifecycle (BatchBegin/BatchEnd, DebugBatchBegin) is left implicit for a tool that cannot be used standalone.

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% and the schema already states 'give this or numbers, not both' and the ordering guarantee. The description's 'takes one number or a list of numbers' and 'unknown number answers as unknown' add only marginal semantics beyond the schema, so baseline 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?

States a specific verb and resource: it answers the calls of the last executed batch by number. An agent can tell this is a read-back of prior batch results rather than a batch-start/end control. It stops short of naming BatchBegin/BatchEnd as the lifecycle siblings it depends on, so differentiation relies on inference.

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 last executed batch" implies the tool is only meaningful after a batch has run, and the description notes takes one number or a list. There is no explicit when-not guidance, no statement that BatchBegin must precede it, and no advice on what to do when a number is unknown beyond the bare 'answers as unknown'.

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