sap_delete_entity

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

No annotations are provided, so the description carries the full burden of behavioral disclosure. 'Delete an entity' implies a destructive mutation, but it doesn't specify permissions required, whether deletion is reversible, error handling, or side effects. For a destructive tool with zero annotation coverage, this is a significant gap in transparency, though it at least correctly indicates a delete action.

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 extremely concise with 'Delete an entity', a single sentence that front-loads the core action. There is no wasted text or redundancy, making it efficient for quick understanding, though it may be overly brief for such a critical operation.

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 complexity of a destructive delete operation with three parameters, no annotations, and no output schema, the description is incomplete. It fails to address key aspects like what happens post-deletion, error scenarios, or how it integrates with sibling tools (e.g., sap_create_entity). The minimal description leaves too many gaps for safe and effective use.

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 input schema fully documents the three parameters (serviceName, entitySet, keyValues). The description adds no additional meaning beyond what the schema provides, such as examples or context for the parameters. With high schema coverage, the baseline score is 3, as the description doesn't compensate but also doesn't detract.

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 'Delete an entity' states the action (delete) and resource (entity), which is clear but vague. It doesn't specify what type of entity or distinguish it from sibling tools like sap_delete_entity (if it existed) or other deletion operations. It's a minimal viable description that conveys the basic purpose without specificity.

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 guidance is provided on when to use this tool versus alternatives. It doesn't mention prerequisites (e.g., needing a connection via sap_connect), exclusions, or comparisons to siblings like sap_update_entity or sap_create_entity. The description lacks any context for usage, leaving it to the agent to infer based on tool names alone.

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