SAPWrite

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

No annotations are provided, so the description must cover behavioral traits. It mentions inheriting safety guards (ALLOW_WRITE/DELETE, role, audit) which gives some context, but fails to disclose important details like error behavior, idempotency, rate limits, or what happens on failure. The inclusion of 'delete' implies destructiveness but is not elaborated.

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 (three sentences) and front-loads the purpose. It avoids redundancy and directly states the delegation mechanism. However, it could be more structured with bullet points for the operation list to improve readability.

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 (18+ operations, dynamic args) and lack of output schema, the description is incomplete. It does not explain return values, error handling, prerequisites, or how to determine the correct operation for a task. Users are left to infer from the operation list without guidance.

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% with descriptions for both parameters. The description adds value by clarifying that 'args' must match the shape expected by the granular tool for a given operation, which is not evident from the schema alone. This dynamic structure is hinted, though no per-operation details are provided.

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 it is a 'Consolidated WRITE verb' that delegates by operation, listing many specific write operations. This distinguishes it from sibling tools like SAPRead (read) and SAPSearch (search), though it doesn't explicitly differentiate from potential granular write tools that might exist outside the sibling list.

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 implies use for writing SAP objects but does not explicitly specify when to use this consolidated tool versus alternatives (e.g., if there were separate tools per operation). It lacks when-not-to-use guidance or scenarios where other tools would be preferred.

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