sap_get_service_metadata

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.