Execute Entity Operation

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

With no annotations provided, the description carries the full burden and discloses key behavioral traits: it's a direct CRUD operation tool (implying mutations), requires authentication, and has strict syntax requirements. However, it lacks details on error handling, rate limits, or specific permissions needed, leaving some gaps.

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 highly concise and front-loaded: it starts with a warning symbol for attention, states the core purpose in the first sentence, provides usage guidelines in the second, and ends with authentication requirements. Every sentence adds critical value with zero waste.

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 (5 parameters, CRUD operations, no output schema, and no annotations), the description is largely complete: it covers purpose, usage, and key behavioral aspects. However, it could benefit from more details on output format or error scenarios to fully compensate for the lack of annotations and output schema.

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 schema already documents all parameters thoroughly. The description adds minimal semantic context by mentioning 'OData queries' and 'CRUD operations,' which aligns with the 'operation' enum and 'queryOptions,' but doesn't provide additional meaning beyond what the schema offers.

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 'Direct CRUD operations on SAP entities with precise OData queries,' specifying the exact verb (execute CRUD operations), resource (SAP entities), and method (OData queries). It distinguishes from sibling tools like 'natural-query-builder' by emphasizing precise syntax requirements.

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?

It provides explicit guidance: 'Use ONLY when you have exact OData query syntax (not natural language). For natural language queries, use natural-query-builder FIRST.' This clearly defines when to use this tool versus alternatives, including prerequisites (exact syntax) and exclusions (natural language).

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