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. It states the action ('Call') but doesn't describe what happens during execution—such as whether it requires authentication, how errors are handled, if it's idempotent, or what the typical response format is. For a tool that likely interacts with external systems, this lack of behavioral context is a significant gap.

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 a single, efficient sentence that directly states the tool's purpose without unnecessary words. It's front-loaded with the core action and target, making it easy to parse. Every part of the sentence earns its place by conveying essential information concisely.

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 calling OData functions (involving external systems, parameters, and potential side effects), the description is insufficient. There are no annotations to cover behavioral aspects, no output schema to describe return values, and the description lacks context on usage, prerequisites, or error handling. This leaves significant gaps for an agent to use the tool effectively.

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?

The schema description coverage is 100%, with clear descriptions for all parameters (serviceName, functionName, parameters). The description adds no additional semantic information beyond what's in the schema, such as examples of valid service names or how parameters map to OData functions. Given the high schema coverage, a baseline score of 3 is appropriate, as the schema does the heavy lifting.

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 the action ('Call') and target ('an OData function import'), which is specific and unambiguous. It distinguishes this tool from siblings like sap_create_entity or sap_query_entity_set by focusing on function calls rather than entity operations. However, it doesn't explicitly differentiate from all siblings (e.g., sap_get_service_metadata might also involve OData services).

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 no guidance on when to use this tool versus alternatives. It doesn't mention prerequisites (e.g., needing a connection via sap_connect), typical use cases for OData functions, or when to choose this over other SAP tools like sap_query_entity_set. Without such context, the agent must infer usage from the tool name alone.

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

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

With no annotations provided, the description carries full burden for behavioral disclosure. 'Connect' implies establishing a session or authentication, but it doesn't describe what happens after connection (e.g., session persistence, authentication mechanism, error handling, or what 'connection' means in this context). For a tool with 7 parameters and no annotation coverage, this is inadequate.

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 a single, efficient sentence that gets straight to the point with zero wasted words. It's appropriately sized for a connection tool and front-loaded with the essential action, making it easy for an agent to parse quickly.

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 connecting to an SAP OData service (involving authentication, session management, etc.), no annotations, and no output schema, the description is insufficient. It doesn't explain what the connection enables, how long it lasts, error conditions, or what the tool returns. For a foundational tool in an SAP integration suite, this leaves critical gaps.

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 7 parameters thoroughly. The description adds no additional parameter information beyond what's in the schema, meeting the baseline score of 3 for high schema coverage. No compensation is needed since schema coverage is complete.

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 'Connect to SAP OData service' clearly states the verb ('Connect') and resource ('SAP OData service'), making the purpose immediately understandable. However, it doesn't differentiate from sibling tools like 'sap_disconnect' or 'sap_connection_status' that also relate to connection management, so it doesn't reach the highest score.

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 no guidance on when to use this tool versus alternatives. It doesn't mention prerequisites, when this should be called before other SAP operations, or how it relates to siblings like 'sap_disconnect' or 'sap_connection_status'. This leaves the agent without context for proper tool selection.

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

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

With no annotations provided, the description carries the full burden of behavioral disclosure. It states the tool checks status and gets info, implying a read-only operation, but doesn't specify details like whether it requires an active connection, what info is returned (e.g., version, latency), or any side effects. This is a significant gap for a tool that might be critical in a workflow.

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 a single, clear sentence with no wasted words. It's front-loaded with the core action ('Check SAP OData connection status') and adds a clarifying detail ('get connection info'). Every part earns its place, making it highly concise and well-structured.

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 SAP tools and the lack of annotations and output schema, the description is incomplete. It doesn't explain what 'connection info' includes, how the status is reported (e.g., success/failure codes), or prerequisites like needing an established connection. For a diagnostic tool in a technical context, more detail is warranted to guide the agent effectively.

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?

The tool has 0 parameters, and the schema description coverage is 100%, so there's no need for parameter details in the description. The description appropriately doesn't mention parameters, which is efficient. A baseline of 4 is applied since it avoids redundancy and focuses on the tool's purpose.

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 the tool's purpose with a specific verb ('Check') and resource ('SAP OData connection status'), and it adds 'get connection info' to clarify the output. However, it doesn't explicitly differentiate this from sibling tools like 'sap_connect' or 'sap_disconnect', which might also relate to connection management, so it doesn't reach the highest score.

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 no guidance on when to use this tool versus alternatives. It doesn't mention scenarios like verifying connectivity before operations, troubleshooting, or how it differs from siblings such as 'sap_connect' (which might establish a connection) or 'sap_disconnect' (which might end one). This lack of context leaves the agent without usage direction.

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

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

With no annotations, the description carries the full burden of behavioral disclosure. It states the tool creates an entity but doesn't mention critical aspects like authentication requirements, error handling, side effects (e.g., database writes), or response format. This is inadequate for a mutation tool with zero annotation coverage.

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 a single, efficient sentence that directly states the tool's purpose without unnecessary words. It is appropriately sized and front-loaded, making it easy to parse quickly.

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 creation tool with no annotations and no output schema, the description is insufficient. It doesn't cover behavioral traits, usage context, or output details, leaving significant gaps for an agent to understand how to invoke and interpret results effectively.

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?

The schema description coverage is 100%, so parameters are well-documented in the schema itself. The description adds no additional semantic context beyond what's in the schema (e.g., examples of 'entity data' or clarification on 'serviceName'), resulting in a baseline score of 3.

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 the action ('Create') and resource ('new entity in an entity set'), making the purpose understandable. However, it doesn't differentiate from sibling tools like sap_update_entity or specify what constitutes an 'entity' in this context, which would be needed for a perfect score.

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 like sap_update_entity or sap_get_entity. The description lacks context about prerequisites (e.g., needing a connection via sap_connect) or typical use cases, leaving the agent to infer usage from the tool name alone.

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

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.

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. It states the action ('disconnect') but does not describe what this entails—whether it terminates a session, releases resources, affects other tools, or has side effects. For a tool with zero annotation coverage, this leaves significant behavioral 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 a single, clear sentence with no wasted words. It is front-loaded and efficiently conveys the core purpose without unnecessary elaboration.

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 simplicity (0 parameters, no output schema) and lack of annotations, the description is minimally adequate. It states what the tool does but lacks details on behavioral impact or usage context, which could be important for an agent managing SAP connections.

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?

The input schema has 0 parameters with 100% coverage, so no parameter documentation is needed. The description does not add parameter details, which is appropriate. A baseline of 4 is applied as it meets the requirement for a zero-parameter tool.

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 'Disconnect from SAP OData service' clearly states the action (disconnect) and the target resource (SAP OData service). It specifically distinguishes this tool from its siblings like 'sap_connect' and 'sap_connection_status', which handle connection establishment and status checking respectively.

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 usage context—disconnecting from an active SAP OData service connection—but does not explicitly state when to use it versus alternatives. It suggests usage after a connection is established (via 'sap_connect'), but lacks explicit guidance on prerequisites or exclusions.

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

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

With no annotations provided, the description carries full burden but offers minimal behavioral insight. It implies a read-only operation ('Get'), but doesn't disclose authentication needs, error handling, rate limits, or what happens if the entity doesn't exist. For a tool with no annotation coverage, this leaves significant gaps in understanding its behavior.

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 a single, efficient sentence with zero waste. It's front-loaded with the core action and resource, making it easy to parse quickly. Every word contributes directly to the purpose without unnecessary elaboration.

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 (OData entity retrieval with key values), lack of annotations, and no output schema, the description is insufficient. It doesn't explain the return format, error cases, or dependencies (e.g., requiring an active SAP connection). For a tool with three parameters and no structured safety hints, more context is needed.

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 three parameters. The description adds no additional meaning beyond implying key-based lookup, which is already suggested by the parameter names. It doesn't explain parameter relationships or provide examples, so it meets the baseline but adds no extra value.

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 the verb ('Get') and resource ('a specific entity'), making the purpose understandable. It distinguishes from siblings like sap_query_entity_set (which queries sets) and sap_create_entity/update_entity/delete_entity (which modify entities). However, it doesn't specify the exact resource type (e.g., OData entity) or explicitly mention it's for retrieval by key, which prevents a perfect score.

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 no guidance on when to use this tool versus alternatives. It doesn't mention when to choose sap_get_entity over sap_query_entity_set (for querying vs. direct key lookup) or sap_get_service_metadata (for metadata vs. data). There's no context about prerequisites (e.g., needing a connection) or exclusions, leaving usage unclear.

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

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. It states the tool gets metadata but doesn't describe what the metadata includes (e.g., entity sets, properties, operations), whether it's a read-only operation, any authentication or rate limit requirements, or error handling. This leaves significant gaps for a tool interacting with a system like SAP.

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 a single, clear sentence with zero waste—it directly states the tool's purpose without unnecessary words. It's appropriately sized for a simple tool and front-loaded with the essential information, making it efficient for an AI agent to parse.

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 SAP/OData systems and the lack of annotations and output schema, the description is incomplete. It doesn't explain what metadata is returned (e.g., structure, format) or behavioral aspects like error cases. For a tool that likely provides critical system information, more context is needed to guide 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?

The input schema has 100% description coverage, with the parameter 'serviceName' documented as 'Name of the OData service'. The description adds no additional meaning beyond this, such as examples of service names or format constraints. With high schema coverage, the baseline score of 3 is appropriate, as the schema does the heavy lifting.

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 the action ('Get metadata') and target ('for a specific OData service'), which is specific and unambiguous. It distinguishes this from siblings like sap_get_services (which likely lists services) and sap_get_entity (which retrieves data entities). However, it doesn't explicitly differentiate from all siblings, such as sap_connection_status, which might also provide metadata about connections.

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 no guidance on when to use this tool versus alternatives. It doesn't mention prerequisites (e.g., needing an active connection via sap_connect), exclusions, or comparisons to siblings like sap_get_services (which might list services without detailed metadata). Usage is implied only by the tool name and description, lacking explicit context.

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

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

With no annotations provided, the description carries full burden for behavioral disclosure. It states what the tool does but provides no information about permissions required, rate limits, pagination, error conditions, or what format the returned list takes. For a tool that presumably returns a list of services, this leaves significant behavioral questions unanswered.

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 a single, clear sentence that states exactly what the tool does with no wasted words. It's appropriately sized for a simple tool with no parameters and gets straight to the point.

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?

For a zero-parameter tool with no output schema, the description provides the basic purpose but lacks important context. It doesn't explain what information is returned about each service, how the list is structured, or how this discovery tool relates to other SAP tools in the server. Given the complexity of SAP systems and the presence of related tools like 'sap_get_service_metadata', more context would be helpful.

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?

The tool has zero parameters with 100% schema description coverage, so the schema already fully documents the parameter situation. The description appropriately doesn't mention parameters since there are none, which is correct for this case. Baseline for zero parameters is 4.

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 the action ('Get list') and the resource ('available OData services'), making the purpose immediately understandable. However, it doesn't distinguish this from its sibling 'sap_get_service_metadata' which likely provides metadata about a specific service rather than listing available services.

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 no guidance on when to use this tool versus alternatives. It doesn't mention when this tool should be used (e.g., to discover available services before calling other tools) or when not to use it, nor does it reference any sibling tools like 'sap_get_service_metadata' that might serve related purposes.

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

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

With no annotations provided, the description carries full burden but only states basic functionality without disclosing behavioral traits. It lacks details on authentication needs, rate limits, error handling, or response format (e.g., JSON structure, pagination behavior). This is inadequate for a query tool with complex parameters.

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 a single, efficient sentence that front-loads the core purpose and key capabilities. It wastes no words and is appropriately sized for the tool's complexity, making it easy for an agent to parse quickly.

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 (8 parameters, no annotations, no output schema), the description is incomplete. It doesn't explain return values, error cases, or how parameters interact (e.g., OData syntax for 'filter'), leaving significant gaps for an agent to invoke the tool correctly in a real SAP OData context.

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 fully documents all 8 parameters. The description adds no additional meaning beyond implying support for filtering, sorting, and pagination—which is already evident from parameter names like 'filter', 'orderby', 'top', and 'skip'. Baseline 3 is appropriate as the schema does the heavy lifting.

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 the action ('Query') and target ('OData entity set') with specific capabilities ('filtering, sorting, and pagination'). It distinguishes from siblings like sap_create_entity or sap_delete_entity by focusing on read operations, though it doesn't explicitly differentiate from sap_get_entity which might also retrieve data.

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 explicit guidance on when to use this tool versus alternatives like sap_get_entity or sap_get_service_metadata. The description implies usage for querying with advanced options but doesn't specify scenarios, prerequisites, or exclusions, leaving the agent to infer based on parameter names alone.

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

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

With no annotations provided, the description carries full burden for behavioral disclosure. 'Update an existing entity' implies a mutation operation but doesn't specify permissions required, whether changes are reversible, potential side effects, error handling, or response format. This leaves critical behavioral traits undocumented for a tool that modifies data.

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 just three words ('Update an existing entity'), making it front-loaded and free of unnecessary information. Every word contributes directly to stating the tool's purpose without any 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 of updating SAP OData entities (4 parameters, nested objects, no output schema, and no annotations), the description is insufficient. It lacks details on authentication, error cases, what constitutes a valid update, or how to interpret results, making it incomplete for safe and effective use in this context.

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%, with all parameters clearly documented in the input schema (serviceName, entitySet, keyValues, data). The description adds no additional parameter semantics beyond what the schema provides, so it meets the baseline score of 3 for adequate but not enhanced parameter documentation.

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 'Update an existing entity' clearly states the verb ('Update') and resource ('entity'), making the basic purpose understandable. However, it doesn't specify what kind of entity (SAP OData entity) or distinguish it from sibling tools like sap_create_entity or sap_delete_entity, leaving the scope vague.

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 no guidance on when to use this tool versus alternatives. It doesn't mention prerequisites (like needing an active SAP connection), differentiate from sap_create_entity (for new entities) or sap_delete_entity (for removal), or specify use cases for updating versus other operations.

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