sap_get_field_metadata

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

With no annotations provided, the description carries the behavioral disclosure burden. It explains what the tool returns: field classifications, currency mappings, customer-role distinctions, status/flag filter recommendations, date fields, and currency fields. This goes beyond the name and schema, though it does not discuss side effects, auth, or rate limits; for a metadata lookup these are less critical.

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 dense and well-organized: a lead sentence, a scannable list of return categories, a bolded usage directive, and a clarifying example. Every sentence earns its place with no filler or repetition.

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 tool with no parameters and no output schema, the description covers what is returned and when to use it. The only ambiguity is that it doesn't state how the target SAP table is determined (e.g., explicitly vs. a currently selected context), but the rest of the guidance is sufficient for an agent to invoke it correctly.

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 is empty with zero parameters, and schema coverage is 100%, so there are no parameter semantics to clarify. The baseline for a zero-parameter tool is 4; the description adds useful context about how the returned metadata should influence query construction.

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 states a specific verb-action ('Get enriched metadata') and a precise resource ('SAP table fields'), then details semantic classifications. The example ('use KUNAG not KUNRG') clearly distinguishes this tool from generic table-reading or structure-reading siblings.

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 gives explicit usage timing: 'USE THIS BEFORE building queries to understand which fields to use!' and a concrete example showing how to pick the correct field by role. However, it does not explicitly name alternatives or state when not to use this tool, so it falls short of a 5.

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