SAPRead

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

No annotations are provided, so the description carries full burden. It only states delegation and argument passing, but does not disclose safety (e.g., read-only nature), side effects, authentication, or rate limits. For a read tool, more safety context would be beneficial.

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 concise with three sentences: purpose, operation list, and usage rationale. No filler or redundant information. Well-structured and front-loaded.

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?

Given the tool's complexity (delegation to 10+ operations) and no output schema, the description lacks return value details, error handling, or examples. It is incomplete for an agent to understand what each operation returns.

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 coverage is 100%, so baseline is 3. The description adds that 'args' must match the underlying granular tool's shape, which provides extra context beyond the schema description. However, it largely repeats the operation enum from the schema.

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 identifies the tool as a consolidated READ verb that delegates to multiple operations, listing all available operations. This distinguishes it from siblings like SAPWrite, though it doesn't explicitly contrast with each sibling.

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 provides a use case: wanting a smaller tool surface instead of 50 granular tools. However, it does not mention when NOT to use it or specify alternatives (e.g., the underlying granular tools are not listed as siblings).

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